Menu
Community /Pin to ProfileBookmark
@NogDogFeb 24.2009 — #I have not made an extensive search, but the only free ones I've seen pretty much all do the same thing: wrap up the code in several layers of base64_encode()-ing and eva() statements. To me these are pretty much a waste of time, as (a) it's not all that hard to "decrypt" them, and (b) using them adds additional processing and resource usage which seems a bit expensive for the limited protection they offer. You can probably get almost as much protection without the overhead if you use some source code obfuscator that will strip out all comments, remove indentation, and rename variables to meaningless names.
But if you find anything good, I'm sure we'd all like to know. ?@NogDogFeb 24.2009 — #I have not used any of them. (So far anything I've done for clients is owned by them, not me, and I've not yet written anything for myself that I feel is worth worrying about this.) All things being equal (which they never are, mind you) I'd probably lean towards Zend just because of their PHP reputation and the likelihood of a good-sized and helpful user base if you need assistance.
Encrypt and Licence?
Hello,
I am building a website for a client and they are also a web developer (they sub-contracted me for a job). They requested that I build a web app for THEIR client and host it on THEIR server. I asked them if it was okay if I protect myself and my code by encrypting it and putting a license on it so that only that client can use my code.
Here are my questions:
1. How do I establish a system that is linked to an external database of priviledged sites that I have that are allowed access to my code. For example, I have a hashed value (Server_Name + Int) + Remote_Host. I basically want to restrict access from website that is not listed in that database of authenticated users.
2. Is there FREE software out there that I can use to encrypt my PHP code (I looked at IonCube, but it is fairly expensive).
Sign in
to post a comment3 Comments(s) ↴
0
@NogDogFeb 24.2009 — #I have not made an extensive search, but the only free ones I've seen pretty much all do the same thing: wrap up the code in several layers of base64_encode()-ing and eva() statements. To me these are pretty much a waste of time, as (a) it's not all that hard to "decrypt" them, and (b) using them adds additional processing and resource usage which seems a bit expensive for the limited protection they offer. You can probably get almost as much protection without the overhead if you use some source code obfuscator that will strip out all comments, remove indentation, and rename variables to meaningless names.But if you find anything good, I'm sure we'd all like to know. ?
0
@NogDogFeb 24.2009 — #