Many intelligent and dedicated people have tried to accomplish
copy protection. In the end, it was almost all wasted effort.
My informed advice: Don't bother trying.
-- Chip Salzenberg, Free-Floating Agent of Chaos | [reply] |
| [reply] [d/l] |
In fact, I do not try to protect a Perl script but a Java application. Since Java does not really have any mechanism to access the hardware and create a key I was hoping to do it through Perl and pass the CPU ID or something like that back to Java.
Any ideas?
Thanks,
Chris
| [reply] |
| [reply] [d/l] |
Anyone who can read/write the script can hack it to avoid your checking mechanisms. There's no use in copy protecting your scripts.
Same goes for Java, as even .class files can be decompiled.
see this page or this one for examples.
"Only Bad Coders Code Badly In Perl" (OBC2BIP)
| [reply] |
The other posting do have valid points. 1) It will be easy to defeat protection in interperted languages. 2) Unless you spend a lot of time on the problem, it's not worth it.
If you really do need serious copy protection for your killer app, you should just purchase a pre-built solution from a vendor. You can find hardware key solutions from Aladdin and Rainbow Technology.
One final thought. All of these copy protection methods only attempt to make the cost of stealing the software much higher. There is no way to achieve perfect protection on the PC. | [reply] |