Hi James,
1) creating a "read only" temp variable where we generate a pub/priv key pair, encrypt that variable, and then destroy the public key.
ECIES uses a temporary public key
2) Creating a basic licensing mechanism, where the app can only decrypt the license for validation, there by preventing the reverse engineering of a license generator.
The setup program would perform the validation, and then save to the Registry (using AES for example). If validation is not performed during setup, another can of worms... The main program reads the registry key then unencrypts. For an AES Encrypted Registry implementation, see http://www.codeproject.com/system/AESEncRegKey.asp Jeff On 1/19/07, James <[EMAIL PROTECTED]> wrote:
Hi Wei. Thank you for the quick response. I've been kicking around several ideas... 1) creating a "read only" temp variable where we generate a pub/priv key pair, encrypt that variable, and then destroy the public key. 2) Creating a basic licensing mechanism, where the app can only decrypt the license for validation, there by preventing the reverse engineering of a license generator. These situtations could easily be handled with RSA and Signatures, Signature with Recovery sounds like a nice alternative. Just some Ideas. James >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [EMAIL PROTECTED] More information about Crypto++ and this group is available at http://www.cryptopp.com. -~----------~----~----~----~------~----~------~--~---
