There are many, many, many protections available. The key is:
- Assessing your target audience, and what they're willing to put up with
- Understanding your audience's desire to play with no pay
- Assessing the amount someone is willing to put forth to break your protection
- Applying just enough protection to prevent most people from avoiding payment, while not annoying those that use your software.
Nothing is unbreakable, so it's more important to gauge these things and pick a good protection than to simply slap on the best (worst) protection you are able to afford.
- Simple registration codes (verified online once).
- Simple registration with revokable keys, verified online frequently.
- Encrypted key holds portion of program algorithm (can't just skip over the check - it has to be run for the program to work)
- Hardware key (public/private key cryptography)
- Hardware key (includes portion of program algorithm that runs on the key)
- Web service runs critical code (hackers never get to see it)
And variations of the above.
与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
