by Dave Johnston » Jun 4, 2002 @ 6:44pm
It might be worth considering a few facts.
1. Until we get DNA fingerprinting for handhelds, it won't be possible to assign a copy of some software to some human owner - therefore perfection in a protection scheme is not possible.
2. What's the nature of the software? Can it be tied to a specific device/ID or is it likely to traverse several generations?
3. What links can be drawn between the purchaser of the software and the software itself?
(4. Not everyone has a credit card.)
Serial numbers are historically the best purchaser<->software link, but they can be distributed. However, they do allow for software to go across several generations of hardware and/or allow the customer to have the same program on several of their own devices (if the EULA allows this)...
Essentially, a protection scheme must in general allow for these:
1. Original customer to use software on different devices over a period of time (max 2/3 years?)
2. A scheme which means that each time the software goes from unregistered to registered status, the location of the user is logged somewhere and perhaps confirmed - maybe through a credit card check? Pirates rarely want to give out personal details, especially if they have to be confirmed in person.
[This is a really rough post with lots of holes, but I can't think right now!]
What can a developer REALLY do
