Received: from smtp017.mail.yahoo.com (smtp017.mail.yahoo.com [216.136.174.114]) by postgresql.org (8.11.3/8.11.1) with SMTP id f66EvQa03396 for ; Fri, 6 Jul 2001 10:57:26 -0400 (EDT) (envelope-from chrup999@yahoo.com) Received: from proxy.compucom.com (HELO Z161842) (204.214.145.2) by smtp.mail.vip.sc5.yahoo.com with SMTP; 6 Jul 2001 14:57:15 -0000 X-Apparently-From: Message-ID: <004101c1062b$f0fa9940$5dd26383@corp.compucom.com> From: "Chris Ruprecht" To: "p-php" Subject: Making things 'tamper proof' Date: Fri, 6 Jul 2001 09:57:13 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200107/1 X-Sequence-Number: 457 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