Re: Serial number verification / obfuscation (was: Re: Hiding
Re: Serial number verification / obfuscation (was: Re: Hiding
- Subject: Re: Serial number verification / obfuscation (was: Re: Hiding
- From: Andrew Merenbach <email@hidden>
- Date: Sat, 27 Jul 2002 23:13:41 -0700
I'm not anywhere past the level of amateur cryptographer, and I doubt
any of the code algorithms I've created are hack-proof in the least.
I think, however, that a system wherein each code is custom-tailored to
the machine it runs on is an ingenious solution. It saves the trouble
of requiring an internet connection to register.
Ah, but the problem is, of course: what if someone has bought the
software on one machine, but they're buying it to use on another
machine, such as a kiosk, or a computer at their laboratory?
Another option would be to include a registration function in the
program which registers over the internet just once, so a kiosk wouldn't
be an issue. But that's a pain, no?
The only method that end-users would really tolerate, I feel, is the
tried-and-true method of a registration key generated by the programmer,
which the end user types into their program, no matter what machine it's
on.
From there, there are two other options. One is to reverse-engineer the
code within the program to verify if it does in fact match up with the
name the user has entered.
The other is to do the reverse of that: take the user's name, and turn
it into a registration code, then see if it matches up with the code the
user entered.
Is there a consensus on which is "safer," i.e. more hack-proof?
Take care,
Andrew Merenbach
_______________________________________________
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.