Dear software protection developers
You know, you don't have to be this helpful :)
(To those who don't quite get it: software protection schemes depend on obfuscation, because the computer is ultimately under control of the end user. That is a corollary to "if the attacker has physical access, you've already lost". Thus, naming functions things like "decryptClass" (since this is a Java protection library) or "VerifyLicense" is... not exactly wise.)
This entry was originally posted at http://davv.dreamwidth.org/36608.html. You may comment there using OpenID, or comment here if you prefer.
(To those who don't quite get it: software protection schemes depend on obfuscation, because the computer is ultimately under control of the end user. That is a corollary to "if the attacker has physical access, you've already lost". Thus, naming functions things like "decryptClass" (since this is a Java protection library) or "VerifyLicense" is... not exactly wise.)
This entry was originally posted at http://davv.dreamwidth.org/36608.html. You may comment there using OpenID, or comment here if you prefer.