Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was wondering what options do we have? PHP is open, I know. But what if I want to bind my work to one server, so that a client could not resell / steal my work. I run my own server, so I can provide a remote authorization mechanism, but I’m not yet aware of any.
What options do we have? Zend is paid and useless because of DeZender; ditto ionCube. So, what are our protection options?
No app is safe if it is on customer’s premises, whatever the technology is. So the only way to keep is safe is just to self-host it… The harder you try, the more bugs and performance losses you introduce, and the result is always uncertain.
Ioncube and zend are options which help you to discourage reverse engineering and access to code, but they won’t stop a determined user.
But remember that the tecnical mean is always just a part of the game. The other part is a properly written and signed EULA or agreement with your customer.