I guess with a CRC check, BlitzKey will be hacker-proof enough for most applications.
The codes generated with this are absolutely un-decryptable. The only problem would occur when the hacker uses the DLL to generate a valid code (only possible if the hacker found the code key you use to generate codes) or like fredborg said, replace the DLL.
I'll probably add in an include file to BlitzKey to CRC check the DLL for you.
Also, I have a question to someone who knows more about this than me: In this code, is it possible for the "SECRET KEY" to be stolen by a hacker:?
I'm not sure if data would be safe this way, since maybe a hacker could check what's in a register or stack (or however function arguments are passed).
The codes generated with this are absolutely un-decryptable. The only problem would occur when the hacker uses the DLL to generate a valid code (only possible if the hacker found the code key you use to generate codes) or like fredborg said, replace the DLL.
I'll probably add in an include file to BlitzKey to CRC check the DLL for you.
Also, I have a question to someone who knows more about this than me: In this code, is it possible for the "SECRET KEY" to be stolen by a hacker:?
ActivationCode$ = GenerateCode("Customer Name", "[SECRET KEY]")
I'm not sure if data would be safe this way, since maybe a hacker could check what's in a register or stack (or however function arguments are passed).