| From: | Phil Davey <pd213(at)mole(dot)bio(dot)cam(dot)ac(dot)uk> |
|---|---|
| To: | p-php <pgsql-php(at)postgresql(dot)org> |
| Subject: | Re: Making things 'tamper proof' |
| Date: | 2001-07-06 16:03:08 |
| Message-ID: | Pine.SGI.4.33.0107061701550.1603082-100000@mole.bio.cam.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php |
On Fri, 6 Jul 2001, Chris Ruprecht wrote:
> I am busy developing some applications which will be sold, once complete.
> The .php files, as far as I know, have to be distributed as they are (in
> source code). Is there any way to protect the application so that it can not
> be tampered with? Can I write some stored procedure of some sort which
> prevents people from messing with the code?
Zend Encoder seems to be what you're after.
http://www.zend.com/zend/products.php#encoder
--
Phil Davey
http://www.pod-designs.net/philandjo.html
E-mail pod(at)pod-designs(dot)net ICQ 46295740
Just because you're smart, doesn't mean you can't act stupid....
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martín Marqués | 2001-07-10 08:52:12 | Re: SELECT column name |
| Previous Message | GH | 2001-07-06 15:49:01 | Re: Making things 'tamper proof' |