Not sure if you got my email so I will post in the forum.
Hello. I had one of my customers tell me that in addition to my product's name, there is also a "Enigma Protector" key entry in the registry that is created upon the launch of my program. I would like you to investigate this if it is true. I think it would be wise to hide what protection software your customers use in every possible way.
Secondly. My customer also informed me he was able to delete the license.dat file created and the program was still able to execute. Is this by intention to make the registry a fail-safe secondary option? I was under the impression both the registry AND license file needed to be intact in order to execute the protected file.
Thanks and look forward to your answer. James
Potential security issue
Re: Potential security issue
Hi dynamicfusion,
Yes, you are right, in some cases there is creating a registry key with the name Enigma Protector. There are few cases when it is creating, and it depends on an options you use in protection. Protection has to remember the state, and due to this it writes to registry.
But, I would like to inform you that it is not even potential security issue, it is not an issue at all. If the cracker can't determine what is kind of protection is used for a file just by the first file look, then such cracker won't be able to bypass this protection. So there is absolutely nothing to worry.
Regarding the second question, the logic of this is so: if file is not found in registry, protection tries to find it in the file. It is not necessary to have registration information both in file and in registry, at least one place it enough. Why is it made so? Just because there are cases, when registry or file system may be write protected on the user pc. Due to this, protection will be unable to write registration information in the registry or in the file. In this case, the second storing option helps protection to work as expected, i.e. if file is write protected then write to registry and vice versa.
Yes, you are right, in some cases there is creating a registry key with the name Enigma Protector. There are few cases when it is creating, and it depends on an options you use in protection. Protection has to remember the state, and due to this it writes to registry.
But, I would like to inform you that it is not even potential security issue, it is not an issue at all. If the cracker can't determine what is kind of protection is used for a file just by the first file look, then such cracker won't be able to bypass this protection. So there is absolutely nothing to worry.
Regarding the second question, the logic of this is so: if file is not found in registry, protection tries to find it in the file. It is not necessary to have registration information both in file and in registry, at least one place it enough. Why is it made so? Just because there are cases, when registry or file system may be write protected on the user pc. Due to this, protection will be unable to write registration information in the registry or in the file. In this case, the second storing option helps protection to work as expected, i.e. if file is write protected then write to registry and vice versa.