From: tom <tom@outervention.net>
To: 'p-php' <pgsql-php@postgresql.org>
Subject: RE: Making things 'tamper proof'
Date: Fri, 6 Jul 2001 11:36:55 -0400
Message-ID: <006201c10631$7d60e1f0$51112c81@bellsouth.net> (raw)
In-Reply-To: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com>
The Zend encoder will convert your source files into byte code. You need the
Zend Optimizer installed for it to read these files, but it's also cross
platform code, it'll run anywhere the proper version of PHP/Optmiizer is
installed. Check out http://www.zend.com
-----Original Message-----
From: pgsql-php-owner@postgresql.org
[mailto:pgsql-php-owner@postgresql.org]On Behalf Of Chris Ruprecht
Sent: Friday, July 06, 2001 10:57 AM
To: p-php
Subject: [PHP] Making things 'tamper proof'
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
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
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: tom@outervention.net
Subject: Re: Making things 'tamper proof'
In-Reply-To: <006201c10631$7d60e1f0$51112c81@bellsouth.net>
References: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com> <006201c10631$7d60e1f0$51112c81@bellsouth.net>
* 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