pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: GH <grasshacker@over-yonder.net>
To: Chris Ruprecht <chrup999@yahoo.com>
Cc: p-php <pgsql-php@postgresql.org>
Subject: Re: Making things 'tamper proof'
Date: Fri, 6 Jul 2001 10:49:01 -0500
Message-ID: <20010706104901.A85799@over-yonder.net> (raw)
In-Reply-To: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com>
References: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com>


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



view thread (4+ messages)  latest in thread

Message-ID: <20010706104901.A85799@over-yonder.net>
Permalink:  ../20010706104901.A85799@over-yonder.net/
Also on:    postgresql.org/message-id/20010706104901.A85799@over-yonder.net

 · 

reply

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: grasshacker@over-yonder.net, chrup999@yahoo.com
  Subject: Re: Making things 'tamper proof'
  In-Reply-To: <20010706104901.A85799@over-yonder.net>
  References: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com> <20010706104901.A85799@over-yonder.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