RE: Licences 101 - Copy Protection for Newbies
RE: Licences 101 - Copy Protection for Newbies
- Subject: RE: Licences 101 - Copy Protection for Newbies
- From: Andrew Merenbach <email@hidden>
- Date: Sat, 28 Sep 2002 09:05:52 -0700
Since we have OpenSSL (for instance, we can use the header crypto.h)
and CDSA (one can download the framework from Apple's open-source
site), one might wonder if there's any reason to use an internal
algorithm of our own.
Take care,
Andrew Merenbach
On Monday, September 23, 2002, at 08:12 AM,
email@hidden wrote:
1.) To simplify this and step 6, just check for for a valid
registration number every time the application starts.
2 & 3.) The most secure method here is having some kind of generation
and validation routines. The easiest way to make this relatively
secure is to generate a serial number based on a registration name.
Maybe something like encrypting the name and hashing the result to
generate a serial number would work. Check out MulleCipher to do
this. If you wanted to, you could also store different types of
information in the serial number, like expiration date, number of
copies, etc. This is all up to you.
4.) You could store the value in a file, or you could store the value
in User Defaults (my preference, as it allows you to register on a
per-user basis). You might want to try encrypting the serial number
before it's written out, thus preventing someone from modifying the
serial number external to your application.
5.) This is fine
6.) See 1.)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.