Bug #7187 Updated: open_basedir is broken! Security alert!
| From: | danbeck@php.net | Date: | Thu, 21 Jun 2001 02:33:08 +0000 |
| Subject: | Bug #7187 Updated: open_basedir is broken! Security alert! | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-57498@lists.php.net to get a copy of this message | ||
ID: 7187
Updated by: danbeck
Reported By: dron@usa.net
Old-Status: Open
Status: Closed
Bug Type: Documentation problem
Operating system:
PHP Version: 4.0.3
Assigned To:
Comments:
I'm closing this and re-opening a more detailed bug report. This is only indirectly related to
open_basedir now.
Previous Comments:
---------------------------------------------------------------------------
[2000-10-16 08:19:46] sniper@php.net
Reclassified as documentation problem.
On page:
http://www.php.net/manual/configuration.php
The directives should be somehow grouped better
to see e.g. which ones can be changed with php_value
and which are only changeable with php_admin_value.
--Jani
---------------------------------------------------------------------------
[2000-10-16 08:04:18] dron@usa.net
Fixed in php4.03pl1.
i should use
php_admin_value open_basedir '.'
instead of
php_value open_basedir '.'
Please make it clear in manual.
---------------------------------------------------------------------------
[2000-10-15 17:09:32] sniper@php.net
Should be fixed in php4.03pl1.
--Jani
---------------------------------------------------------------------------
[2000-10-13 12:27:37] dron@usa.net
http://www.php.net/manual/configuration.php
----
open_basedir string
Limit the files that can be opened by PHP to the specified directory-tree.
When a script tries to open a file with, for example, fopen or gzopen, the location of the file is
checked. When the file is outside the specified directory-tree, PHP will refuse to open it. All
symbolic links are resolved, so it's not possible to avoid this restriction with a symlink.
The special value . indicates that the directory in which the script is stored will be used as
base-directory
---
I don't need full path - i want to restrict users from accessing files in upperlevel
directories.
as Mr. Zeev Suraski said:
It's not related to open_basedir, there's a problem in the php_value system in 4.0.3.
---------------------------------------------------------------------------
[2000-10-13 12:20:35] andi@php.net
You should be using full path with the open_basedir directive as far as I know. Can you please try
and let us know of the results?
---------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view the rest of the comments,
please view the bug report online.
ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=7187&edit=2