| From: | GH <grasshacker(at)over-yonder(dot)net> |
|---|---|
| To: | Chris Ruprecht <chrup999(at)yahoo(dot)com> |
| Cc: | p-php <pgsql-php(at)postgresql(dot)org> |
| Subject: | Re: Making things 'tamper proof' |
| Date: | 2001-07-06 15:49:01 |
| Message-ID: | 20010706104901.A85799@over-yonder.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-php |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Phil Davey | 2001-07-06 16:03:08 | Re: Making things 'tamper proof' |
| Previous Message | tom | 2001-07-06 15:36:55 | RE: Making things 'tamper proof' |