To scorillo7: Thanks for the great reply! By the way, how are VB markers working? Still did not get reply from you...?
Daniel wrote:I would like to ask whether there is some CRC check of internal overlays in Enigma. I would like to defeat possible replacement of my overlay with a different one. Just simple CRC or similar.
This is good idea Daniel, I will make it in the nearest release! There are a lot of system that produce overlay executables, it would be great decision to protect overlay data!
scorillo7 wrote:1.check the integrity of Enigma(api)
This is always greeting! Integrity checking could help a lot to avoid cracking. I advice to use it as much as possible (here I mean CheckProtection markers and Inline Patching protection). But these checkups do not help to protect overlay data. Overlay data does not map into process memory, it is just placed into file.
scorillo7 wrote:If you have a history with crackers(your apps is often cracked) do not let entirely on the protector checks, build some custom integrity check(crc32,md5,sha,etc)
It could help much even than you think! Simple protection methods are always help to increase protection.
scorillo7 wrote:The best way is to put a rutine in your apps that check validation of enigma ,something like that:key generated by enigma = 00000 if result is the same then jump is cracked.
Yes, this is old and very known protection trick, but it is still very important. I can even tell that this is perfect decision! You may call key verify routine with the invalid key to check the function result and if it is return true than you will know that protection is damaged.
scorillo7 wrote:I saw on the memberlist of Enigma forum some crackers name. Often this is buying protectors from the authors.
I saw these guys too, moreover, some of these guys are registered customers. But really, not all of them are buying Enigma for cracking and sharing, most of them are really great developers who are using Enigma for own software protection, why not!