.php files - permissions are set public readable - so can public get to see actual raw file?

[Dave Smithz]

Hi there,

As a newbie to PHP is it in anyway possible for a casual web surfer to
actually get to see the PHP behind my .php file.

E.g.

if index.php contained PHP code to check if the page had been called with a
variable such as "password", is there anyway a public member can get to see
the raw php file and therefore see what the password is?

index.php might be:

if ($_REQUEST[password]="secret") {

Then show one page elseshow another page

}

So if a user visits with
index.php?password=secret

they get to see the secret page.
But as the index.php has to have file permission set so that anyone can read
it, I'm worried that the public can just somehow view the file and learn the
password.

Can someone shed any light on this (assuming it makes sense).

Kind regards

Dave.

[Andy Hassall]

On Wed, 26 Jan 2005 00:13:25 -0000, "Dave Smithz" <SPAM FREE WORLD> wrote:

As a newbie to PHP is it in anyway possible for a casual web surfer to
actually get to see the PHP behind my .php file.
Not unless your server is badly misconfigured.
E.g.

if index.php contained PHP code to check if the page had been called with a
variable such as "password", is there anyway a public member can get to see
the raw php file and therefore see what the password is?

index.php might be:

if ($_REQUEST[password]="secret") {

>Then show one page

else

>show another page

}

So if a user visits with
index.php?password=secret

they get to see the secret page.
But as the index.php has to have file permission set so that anyone can read
it, I'm worried that the public can just somehow view the file and learn the
password.

If the "public" is just people who view through the web server, then no,
unless your server config is broken. That rules out "casual web surfers".

However, people logged into the server itself through shell access, or running
their own PHP code on the same server would likely be able to access
public-readable scripts.

--
Andy Hassall / <an**@andyh.co.uk> / <http://www.andyh.co.uk>
<http://www.andyhsoftware.co.uk/space> Space: disk usage analysis tool

[Dave Smithz]

"Andy Hassall" <an**@andyh.co.uk> wrote in message >

If the "public" is just people who view through the web server, then no,
unless your server config is broken. That rules out "casual web surfers".

However, people logged into the server itself through shell access, or running their own PHP code on the same server would likely be able to access
public-readable scripts.

OK, so other users on my server from shared hosting account (like webfusion
or something) would be able to gain access to my raw php files.

So what is ideally a quick and easy way to implement security so that no one
other then the programmers get to see the raw code?
I tried password protected folders, but the problem is that then when we
want the "public" (causal web surfers) to submit information that gets
entered into the DB, they get prompted for username and password.

(See earlier post yesterday titled:
"Maybe easy - securing php files containing DB access passwords etc." )

Any thoughts?

Kind regards

Dave

[Michael Fesser]

.oO("Dave Smithz" <SPAM FREE WORLD>)

OK, so other users on my server from shared hosting account (like webfusion
or something) would be able to gain access to my raw php files.
Probably.
So what is ideally a quick and easy way to implement security so that no one
other then the programmers get to see the raw code?

On many shared hosts there simply is no way, because all PHP scripts run
with the same username. There are ways to run scripts under the username
of their owner, but this has to be configured by the host.

Micha

[Markku Uttula]

Dave Smithz wrote:

So what is ideally a quick and easy way to implement security so
that
no one other then the programmers get to see the raw code?

If the webhost supports it, Zend Encoder. Quick, easy, but definetly
not cheap. On the other hand, if there really is something worth
protecting, the price of Zend Encoder is small to pay for the
protection you get.

--
Markku Uttula