From: Chris Ruprecht <chrup999@yahoo.com>
To: p-php <pgsql-php@postgresql.org>
Subject: Making things 'tamper proof'
Date: Fri, 6 Jul 2001 09:57:13 -0500
Message-ID: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com> (raw)
Hi all,
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?
Best regards,
Chris
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: chrup999@yahoo.com
Subject: Re: Making things 'tamper proof'
In-Reply-To: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com>
References: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox