Allow HardwareID changes feature
Allow HardwareID changes feature
I do not understand fully the "Allow HardwareID changes" feature recently introduced in v1.80. How the program knows that only one,two or whatever number of changes is allowed? When I set number 1 for each portion of Hardware lock (CPU+Motherboard+Harddisk+Windows_serial), does it mean that the whole program can be actually transferred freely to new PC? But if I am able to do it, I can transfer to any number of computers then and there is actually no Hardware lock any more. If so, what is the suggestion for using this feature?
Re: Allow HardwareID changes feature
Hi Daniel, good question.. I also wanted to improve manual regarding this feature, hope you help me 
Listen, if you are allowing few hardware changes, this means that particular selected hardware lock could be changed selected number of times on the user PC.
Imagine that you are getting the registration key that is hardware locked to user. Let's think that this hardware lock is System Volume Name. Once user installed this key, application is working registered well. But after some time, user self, or some 3rd party program, has modified system volume name. New hardware id will be generated and registration key becomes invalid.
To avoid such issues, there is Allow Changes feature. If you set the number of allowed changes above example to 1, then after first changing of system volume name, registration key will still be known as valid.
Regards
Vladimir
Listen, if you are allowing few hardware changes, this means that particular selected hardware lock could be changed selected number of times on the user PC.
Imagine that you are getting the registration key that is hardware locked to user. Let's think that this hardware lock is System Volume Name. Once user installed this key, application is working registered well. But after some time, user self, or some 3rd party program, has modified system volume name. New hardware id will be generated and registration key becomes invalid.
To avoid such issues, there is Allow Changes feature. If you set the number of allowed changes above example to 1, then after first changing of system volume name, registration key will still be known as valid.
Regards
Vladimir
Re: Allow HardwareID changes feature
According to Daniel conception -->
It's possible?
Code: Select all
"does it mean that the whole program can be actually transferred freely to new PC?..."Re: Allow HardwareID changes feature
Actually, what Keygen wrote is what interests me a lot. The number of left changes must be stored somewhere, presumably in registry. But with having this feature enabled for EVERY part of Hardware lock, it might be circumvented.
For example, if I am a bad guy. I know that the program is locked with 1 HardwareID change possibility. I install under FirstDefense-ISR or Rollback Rx (everything works OK). I give away to my friend. He/she installs on his/her PC - again no problem.
That means that at least one hardware lock item should be set to zero to avoid this spread.
Moreover, how this "change" feature works with Encrypt with HardwareID? I think that there is no connection betweenn both features. If hardware changes I will pass HardwareID check but fail afterwards on HardwareID encryption protection. Am I right?
For example, if I am a bad guy. I know that the program is locked with 1 HardwareID change possibility. I install under FirstDefense-ISR or Rollback Rx (everything works OK). I give away to my friend. He/she installs on his/her PC - again no problem.
That means that at least one hardware lock item should be set to zero to avoid this spread.
Moreover, how this "change" feature works with Encrypt with HardwareID? I think that there is no connection betweenn both features. If hardware changes I will pass HardwareID check but fail afterwards on HardwareID encryption protection. Am I right?
Re: Allow HardwareID changes feature
Yes and no.Daniel wrote: does it mean that the whole program can be actually transferred freely to new PC?
No because new PC will have new hardware id, but for the firt registration program will require the hardware id that used for generation of registration key.
Yes because everything is possible. If you think that user is so advanced that could move hardware locked license to another PC, then the user, I seem, is the same clever to just unpack...?
You, guys, should decide self, what is preffer for you, replying on users emails regarding each hardware change, or try to use this feature.
Thanks a great decision! At least one hardware lock will not allow to move license!Daniel wrote:That means that at least one hardware lock item should be set to zero to avoid this spread.
Right Daniel, there is no connection between Allow Changes and Encrypt with Hardware. I did not make this feature compatible with Encrypt with Hardware because it would be a weak place to remove protection... seems...Daniel wrote:Moreover, how this "change" feature works with Encrypt with HardwareID? I think that there is no connection betweenn both features. If hardware changes I will pass HardwareID check but fail afterwards on HardwareID encryption protection. Am I right?
Re: Allow HardwareID changes feature
This is a good decision at all! I suppose license transfer to other PC is quite impossible. 
Re: Allow HardwareID changes feature
I think is a good solution to allow hardware change but it has minor glitch because out there can happend a lot in a user system.The mechanism inside Enigma MUST not allow this option to be valide until the developer has validate more than 3 option (ex: motherboard+cpu type+ hdd serial).Once the user change(from diff case, failure,etc) the hdd ,the mechanism must be capable to recognize the rest of hardware which form the HWID,recognize the same computer.
The best solution is to encrypt the software based on "Hardware ID" option.
The best solution is to encrypt the software based on "Hardware ID" option.
Re: Allow HardwareID changes feature
Surely, Allow Hardware changes is not a very good option, but I've made it mainly due to 2 reasons:
1. Sometimes I get emails from Enigma users that their users alert on invalid key after, for example, few program starts with valid registration. I do not know what is happening on the users pc, maybe they manually change hardware id (like Computer Name and System Volume Name), maybe they had changed installed hardware, maybe they attempt to crack it.. but maybe Enigma fails. Mainly due to last reason it was developed.
2. As per my experience, hardware id changes on users pc, mainly, in only 2 values. So you could enable only 1 hardware changes for each hardware lock that will help you to avoid users emails regarding invalid lisence (that was valid few minutes ago) and the time that you could spend to regenerate new license. Even if the advanced cracker got this license, and he copied license to another PC, what do you think is more important, allow one cracker to use license on another pc, or reply on the users emails and re-generate them license?
Encrypt with Hardware ID is a really nice feature. The main disadvantage is that you need to protect each version for each customer. But it also could be automated. For example, you may develop simple php control panel, access to that your users will have. On the first user requiest, you could protect new version with entered user hardware id directly on the server side by means console version of Enigma (you will only have to have Windows server with possibility to run executables). So the scheme could look like:
1. User purchase program, automated script will generate login and password for control panel
2. User goes to control panel, there he has 1 (at least) possibility to build unique, hardware encrypted version
3. User enters hardware id, clicks on button, php script calls console version of Enigma that protects files and returns result (protected file) to user.
FYI, such control panel (with much more features and possibilities) is in development, soon we release it.
1. Sometimes I get emails from Enigma users that their users alert on invalid key after, for example, few program starts with valid registration. I do not know what is happening on the users pc, maybe they manually change hardware id (like Computer Name and System Volume Name), maybe they had changed installed hardware, maybe they attempt to crack it.. but maybe Enigma fails. Mainly due to last reason it was developed.
2. As per my experience, hardware id changes on users pc, mainly, in only 2 values. So you could enable only 1 hardware changes for each hardware lock that will help you to avoid users emails regarding invalid lisence (that was valid few minutes ago) and the time that you could spend to regenerate new license. Even if the advanced cracker got this license, and he copied license to another PC, what do you think is more important, allow one cracker to use license on another pc, or reply on the users emails and re-generate them license?
Encrypt with Hardware ID is a really nice feature. The main disadvantage is that you need to protect each version for each customer. But it also could be automated. For example, you may develop simple php control panel, access to that your users will have. On the first user requiest, you could protect new version with entered user hardware id directly on the server side by means console version of Enigma (you will only have to have Windows server with possibility to run executables). So the scheme could look like:
1. User purchase program, automated script will generate login and password for control panel
2. User goes to control panel, there he has 1 (at least) possibility to build unique, hardware encrypted version
3. User enters hardware id, clicks on button, php script calls console version of Enigma that protects files and returns result (protected file) to user.
FYI, such control panel (with much more features and possibilities) is in development, soon we release it.