>and then on another note, why do you have users on a webserver who
>aren't developers???
Cause most people aren't.. but they want to create their own apps.. they
think it's a computer and it's software so anyone can do it.. right?? Most
of us know it's a bit harder then that.. oh well.. let t
At 12:08 17-5-01 +0700, Kittiwat Manosuthi wrote:
>In a virtual hosting environment, even though a directory permission is
>set to 751, but you still need to leave world-readable permission on
>individual php file that is to be read from a browser. In a scenario
>where there's another user in the
also sprach Maxim Maletsky (on Thu, 17 May 2001 02:25:47PM +0900):
> no no and no.
oh sure you can. identify the group that apache runs as, then chown
the directories 0750 and files 0640 after chgrp'ing them all to the
same apache group, and you're set. i have my apache run as user
apache and gro
: Thursday, May 17, 2001 2:26 PM
To: 'Kittiwat Manosuthi'; [EMAIL PROTECTED]
Subject: RE: [PHP] way to protect .php file
no no and no.
You can chown the whole directory with it's contents to a specific user
using that directory. In this way no cd is possible.
This should be done au
no no and no.
You can chown the whole directory with it's contents to a specific user
using that directory. In this way no cd is possible.
This should be done automatically when creating user accounts. There are
even softwares to do that - they create you a directory, user, group, add
vhost and
> Is there anyway one can protect this?
Include the passwords from another file that doesn't need
to be web-accessible.
Or, find a virtual host that doesn't allow this kind of
thing :)
Jason
--
Jason Murray
[EMAIL PROTECTED]
Web Developer, Melbourne IT
"What'll Scorpy use wormhole technolog
6 matches
Mail list logo
