Making things 'tamper proof'

Поиск
Список
Период
Сортировка
От Chris Ruprecht
Тема Making things 'tamper proof'
Дата
Msg-id 004101c1062b$f0fa9940$5dd26383@corp.compucom.com
обсуждение исходный текст
Ответы Re: Making things 'tamper proof'  (GH <grasshacker@over-yonder.net>)
Re: Making things 'tamper proof'  (Phil Davey <pd213@mole.bio.cam.ac.uk>)
RE: Making things 'tamper proof'  ("tom" <tom@outervention.net>)
Re: Making things 'tamper proof'  (GH <grasshacker@over-yonder.net>)
Список 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


В списке pgsql-php по дате отправления:

Предыдущее
От: Chris Ruprecht
Дата:
Сообщение: Re: Postgress jobs stick around after they have completed
Следующее
От: GH
Дата:
Сообщение: Re: Making things 'tamper proof'