Received: from draco.over-yonder.net (draco.over-yonder.net [198.78.58.61]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f66Fn8a32955 for ; Fri, 6 Jul 2001 11:49:08 -0400 (EDT) (envelope-from gh@over-yonder.net) Received: by draco.over-yonder.net (Postfix, from userid 1012) id B0D5C62D0A; Fri, 6 Jul 2001 10:49:01 -0500 (CDT) Date: Fri, 6 Jul 2001 10:49:01 -0500 From: GH To: Chris Ruprecht Cc: p-php Subject: Re: Making things 'tamper proof' Message-ID: <20010706104901.A85799@over-yonder.net> References: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com>; from chrup999@yahoo.com on Fri, Jul 06, 2001 at 09:57:13AM -0500 X-OS: FreeBSD X-Archive-Number: 200107/2 X-Sequence-Number: 458 And this has *what* to do with PostgreSQL? On Fri, Jul 06, 2001 at 09:57:13AM -0500, some SMTP stream spewed forth: > > 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? Yes. > Can I write some stored procedure of some sort which > prevents people from messing with the code? No, I don't even know what you are thinking here. The PHP code would have essentially nothing to do with the database. You can obscure PHP source code through the use of the PHP "compiler" by Zend. I do not how difficult it is to reverse engineer code obscured in this manner. "Compiling" PHP code also improves performance also. IIRC, the "compiled" code must still be executed by `PHP`. gh > Best regards, > Chris