Use public key cryptography and place the public key in
your app. Using a key-signer app, create a public-/private-key
pair, and digitally sing the license owner details like
name, postal and email address etc. No need to encrypt this
detail, since your shipped app will later verify, if this the license
owner detail is correctly digitally signed.
Pro:
- Users can't create new license keys
- You need to put a password in your application
Con:
- A bit more complicated.
Am 28.06.2006 um 15:49 schrieb [EMAIL PROTECTED]:
If I hardcode a password into an app in RB, how easy is it for
someone to decompile the app and get the password? Are RB apps
secure in this fashion?
Thanks,
Andrew Keller
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
