Re: new security related directive for php-4.3.4
| From: | boulat at funio dot com | Date: | Fri, 19 Mar 2004 18:19:23 +0000 |
| Subject: | Re: new security related directive for php-4.3.4 | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-8613@lists.php.net to get a copy of this message | ||
> So if your script is:
>
> /path1/path2/path3/foo.php
>
> And your virtual_root_level is set to 2 then foo.php will be able to open
> files anywhere under /path1/path2
>
> How is that different from simply setting open_basedir to /path1/path2 ?
>
> Is it because you have a bunch of different paths for every user and you
> don't want to add all these to your open_basedir list?
Bingo, I have too many clients to add them all, instead determining the
value on the fly is the best way to go IMHO.
> It seems a bit
> fishy to me. There is nothing wrong with have vhost-specific >open_basedir
> settings.
Agreed, but for me it seems that using that directive would save you time
and would make your vhost-specific settings shorter, especially if all
your virtual hosts are located in the same directory-tree.
>
> -Rasmus
>
>
> On Fri, 19 Mar 2004 boulat@funio.com wrote:
>
>> Hi internals,
>>
>> I added "virtual_root_level" new security related directive
>> into php-4.3.4.
>>
>> Full description with the patch can be found in here
>>
>> http://www.boulat.net/projects/virtual_root_level/
>>
>> Some feedback/comments would be appreciated.
>>
>> Regards,
>> Boulat
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>