![]() ![]() If they're located overseas, your only real option is to freeze/appropriate funds from PayPal/credit card. You go to your lawyer, ask him to get a court order telling PayPal/ISP to release the identity of the thief, and then start tracking them down. Their PayPal information or even an IP address should be enough. You'll need to know who leaked the code in the first place for this. If you can track them, you can sue them (or worse). This will give you the ability to track whoever pirated your code. This can be done automatically, and is great to do with obfuscated code (another, complementing method). Add a unique identifier to each version of the script sold. ![]() Someone can still reverse engineer your stuff, but I'll touch on that later. This removes access to your code base, thus preventing direct piracy. This means finding appropriate hosting in the cloud, etc. There are several methods of handling this: There are a few instances where programmers ended up with bullet-proof protection, but it usually involved high-end engineering. It is, as noted by Paul, a form of flattery for you, even though I understand how sorry you may feel. No-cd patches / cracks for new games/softwares now are almost released the same day as the softwares themselves. If there was a magic way to prevent code from being broken, it would have been known for a long time. You may translate it, compress it, or obfuscate it as much as you want, (and it's probably the best thing you can do) you will never fully protect it when released to the public.Īgain. PHP is, like Javascript, an interpreted language. If you are releasing a php framework containing both the server and client code then you have no way of fully protecting yourself. All sensible data should be stored in the server side where it is kept hidden from the user. Hence it should not contain any sensible information such as passwords or such. No matter how much you will obfuscate it, compress it or translate it to some random japanese dialect, it is still source code that the user has access to. ![]() ![]() This is the number one reason why Javascript is not secure. After a few downvotes, I decided to comment on my answer:Īny code that is released public has a chance of being hacked. Do not release sensible source code to the public. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |