Re: Making things 'tamper proof' - Mailing list pgsql-php

From Phil Davey
Subject Re: Making things 'tamper proof'
Date
Msg-id Pine.SGI.4.33.0107061701550.1603082-100000@mole.bio.cam.ac.uk
Whole thread Raw
In response to Making things 'tamper proof'  ("Chris Ruprecht" <chrup999@yahoo.com>)
List 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@pod-designs.net                          ICQ 46295740
Just because you're smart, doesn't mean you can't act stupid....


pgsql-php by date:

Previous
From: GH
Date:
Subject: Re: Making things 'tamper proof'
Next
From: "tom"
Date:
Subject: RE: Making things 'tamper proof'