RE: Making things 'tamper proof'
От | tom |
---|---|
Тема | RE: Making things 'tamper proof' |
Дата | |
Msg-id | 006201c10631$7d60e1f0$51112c81@bellsouth.net обсуждение исходный текст |
Ответ на | Making things 'tamper proof' ("Chris Ruprecht" <chrup999@yahoo.com>) |
Список | pgsql-php |
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)
В списке pgsql-php по дате отправления: