Encrypting code with custom serial numbers?
Posted: Tue Nov 16, 2010 2:05 pm
The reg_crypt_begin/end markers seem to be used to encrypt code that is being decrypted in registered mode. I assume the decryption key depends on the serial number, so that without a valid serial number someone can never decrypt the code.
Now, I already have my own serial number scheme, so I can't use Enigma's Registration module. However, is it still possible to encrypt parts of my code, using a custom encryption key which I specify in the Enigma(64)-project?
I can make sure that I can extract some constant key from my serial numbers. Then, if my app is registered, can I somehow pass this constant number (or its md5 hash or whatever) as a key through any of the API functions and then have my registered-only-code be decrypted with that key?
Thanks!
(edit - FYI: I am considering Enigma as an alternative to ASProtect, which does not support x64 and doesn't seem to be actively developed anymore. ASProtect did offer this feature, called 'encrypt with custom key' and within any .aspr project I could just specify some binary file with the encryption key. Then during runtime I had to call an api function with a pointer to the encryption key. If the key in memory (which was extracted from my serial number) is correct, the code is decrypted. Otherwise, I get random garbage code )
Now, I already have my own serial number scheme, so I can't use Enigma's Registration module. However, is it still possible to encrypt parts of my code, using a custom encryption key which I specify in the Enigma(64)-project?
I can make sure that I can extract some constant key from my serial numbers. Then, if my app is registered, can I somehow pass this constant number (or its md5 hash or whatever) as a key through any of the API functions and then have my registered-only-code be decrypted with that key?
Thanks!
(edit - FYI: I am considering Enigma as an alternative to ASProtect, which does not support x64 and doesn't seem to be actively developed anymore. ASProtect did offer this feature, called 'encrypt with custom key' and within any .aspr project I could just specify some binary file with the encryption key. Then during runtime I had to call an api function with a pointer to the encryption key. If the key in memory (which was extracted from my serial number) is correct, the code is decrypted. Otherwise, I get random garbage code )