Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Machine Code getting change #4

Open
Manthan2611 opened this issue Aug 1, 2019 · 2 comments
Open

Machine Code getting change #4

Manthan2611 opened this issue Aug 1, 2019 · 2 comments

Comments

@Manthan2611
Copy link

Hi,

Sometime i have seen that machine code is getting change on the machine. There was no hardware changes done on the machine.
Sometime it get change after restart and sometime it get changes after using function more than twice.
I have found no solution on it as referring the code found that it generate the machine code based on hardware CPU and board id's. but without changing any of it the machine code gets changed.

What i need to check so that it don't get changed?

Thanks & Regards,
Manthan Patel

@artemlos
Copy link
Contributor

Hey!

Thanks for letting me know.

Could you please try using Helpers.GetMachineCodePI() method in https://www.nuget.org/packages/Cryptolens.Licensing/. It's in SKM.V3.Methods namespace.

That method uses the result from cmd.exe /C wmic csproduct get uuid instead, which I think should work better.

/Artem

@lordofscripts
Copy link

The "Machine Code" used here enumerates the network interfaces prior to generating the machine code and does that without any filtering, same goes for the disk drives, it will also enumerate USB devices. If any of those things change, then your machine code will change. While it may do part of its work, it is rather weak because if you install VMWare for example, a new network interface will be enumerated and the machine code will change rendering the license invalid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants