[thelist] Securing PHP source WAS: Use PHP for content?

Howard Cheng howcheng at ix.netcom.com
Thu Nov 21 16:33:01 CST 2002


PHP source code is secured by making sure the browser can't read the source
-- in short, make it so that the file is processed by the PHP engine.

For example, on camst.net, the frameset is index.html, not index.php, and
thus we can see the PHP source code. You would just make sure that all
files containing PHP code (whether they're .php, .inc, .whatever) are sent
by the web server to the PHP engine. How you do it depends on what web
server you're using.

At 05:13 PM 11/21/2002 -0500, Alex Ezell wrote:
>I searched the web over and thought I found something on securing my PHP
>source, but alas, it was simply about securing my PHP installation.
>
>How does one go about securing their PHP source code?

::::::::::::::::::::::::::::::::::
Howard Cheng
http://www.howcheng.com/ <-- NEW!
howcheng at ix dot netcom dot com
AIM: bennyphoebe
ICQ: 47319315




More information about the thelist mailing list