#22220 [Ver->Csd]: "php_admin_value open_basedir none" does not work

ID: 22220 Updated by: sniper@php.net Reported By: root@mediamonks.net -Status: Verified +Status: Closed Bug Type: Apache related Operating System: FreeBSD 4.7-STABLE PHP Version: 4.3.0 New Comment: This bug has been fixed in CVS. In case this was a PHP problem, snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. In case this was a documentation problem, the fix will show up soon at http://www.php.net/manual/. In case this was a PHP.net website problem, the change will show up on the PHP.net site and on the mirror sites in short time. Thank you for the report, and for helping us make PHP better. Previous Comments: ------------------------------------------------------------------------ [2003-02-15 13:36:38] root@mediamonks.net As there's nothing I can find in the documentation about the 'none' setting I don't know wheter it should turn off the open_basedir or should inherit the default. Both make sense, but if it's the latter then there's no way to turn the open_basedir restriction off, other than '/'. ------------------------------------------------------------------------ [2003-02-15 13:20:25] sniper@php.net I tested that now, and indeed, it doesn't work. ------------------------------------------------------------------------ [2003-02-15 13:18:13] sniper@php.net So this bug's summary should be: "'php_admin_value open_basedir none' does not work" ??? ------------------------------------------------------------------------ [2003-02-15 13:02:19] root@mediamonks.net Actually, I added a comment to 19292 about my problem and it was deleted as not being appropriate there. I am not having trouble with random open_basedir errors, I'm having one simple problem. I have a default open_basedir of '/var/www/' in my php.ini and I used to turn off ('allow all files to be opened') for a particular vhost by setting open_basedir to '/'. Whether this wastes resources I don't know and actually I don't care too, because it does what I want. Starting with 4.3.0 I can't use '/' as open_basedir anymore for some reason, and imo it wasn't thought about properly because it creates contradictory error messages like: [Warning: Unknown(): open_basedir restriction in effect. File(/var/www/host.example.com/root/admin/phpinfo.php) is not within the allowed path(s): (/) in Unknown on line 0] But I couldn't care less if there was an equivalent for setting open_basedir to '/'. Because all I need is to turn off open_basedir for a particular vhost. And I tried setting open_basedir to none, 'none' and "none", but this just leaves the default of '/var/www' in effect. So I'm guessing that the 'none' setting isn't working properly as I would think that it should turn off the open_basedir restriction for the vhost. ------------------------------------------------------------------------ [2003-02-14 08:36:03] iliaa@php.net Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the existing bug instead. Thank you for your interest in PHP. First of all open_basedir of '/' is rather meaningless since it allows opening of every file anyway. Secondly the open_basedir problems especially in FreeBSD enviroment should be convered in bug report #19292. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/22220 -- Edit this bug report at http://bugs.php.net/?id=22220&edit=1