Re: Protecting PHP-code
From: TheLobster at Gmail dot Com (thelobster_at_gmail.com)
Date: 01/05/05
- Next message: CJ Llewellyn: "Re: php adodb data entry form question"
- Previous message: TheLobster at Gmail dot Com: "Re: PHP interpeter or comiler or dubugger of some sort...for Mac?"
- In reply to: Axier: "Protecting PHP-code"
- Next in thread: Erwin Moller: "Re: Protecting PHP-code"
- Reply: Erwin Moller: "Re: Protecting PHP-code"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 5 Jan 2005 13:57:01 -0800
Axier wrote:
> 3. Encrypt it somehow. Would not be my first choice though.
Zend has a REALLY nice way of maing your code secure. It masks the code
and will run it but not allow anyone to edit it. You give a key to the
client so that they can "unlock" and run your script. The key also has
a nice feature where you can set who the code is registred to, set how
long that the script is vaild for (i.e. 14 day trial), how many clients
can connect and use the code and a bunch of other options.
- Next message: CJ Llewellyn: "Re: php adodb data entry form question"
- Previous message: TheLobster at Gmail dot Com: "Re: PHP interpeter or comiler or dubugger of some sort...for Mac?"
- In reply to: Axier: "Protecting PHP-code"
- Next in thread: Erwin Moller: "Re: Protecting PHP-code"
- Reply: Erwin Moller: "Re: Protecting PHP-code"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|