Making things 'tamper proof'

From: "Chris Ruprecht" <chrup999(at)yahoo(dot)com>
To: "p-php" <pgsql-php(at)postgresql(dot)org>
Subject: Making things 'tamper proof'
Date: 2001-07-06 14:57:13
Message-ID: 004101c1062b$f0fa9940$5dd26383@corp.compucom.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-php

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

Responses

Browse pgsql-php by date

  From Date Subject
Next Message tom 2001-07-06 15:36:55 RE: Making things 'tamper proof'
Previous Message Hervé Piedvache 2001-07-03 15:07:19 [PGSQL/PHP] Trouble: pq_recvbuf: unexpected EOF on client connection