Bug #12872 Updated: User-defined safe_mode restrictions
| From: | sniper@php.net | Date: | Fri, 31 May 2002 11:23:25 +0000 |
| Subject: | Bug #12872 Updated: User-defined safe_mode restrictions | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-8999@lists.php.net to get a copy of this message | ||
ID: 12872
Updated by: sniper@php.net
Reported By: hc@saustrup.net
-Status: Open
+Status: Closed
Bug Type: Feature/Change Request
Operating System: Linux
PHP Version: 4.0.6
New Comment:
Thank you for your bug report. This issue has already been fixed
in the latest released version of PHP, which you can download at
http://www.php.net/downloads.php
Previous Comments:
------------------------------------------------------------------------
[2002-05-30 11:11:39] nospam.hc@saustrup.net
It appears the GID-check is implemented in the latest release. You guys
rock! :-)
------------------------------------------------------------------------
[2001-08-21 08:56:55] hc@saustrup.net
I get this warning when using safe_mode:
"Warning: SAFE MODE Restriction in effect. The script whose uid is 503
is not allowed to access ..."
We're currently working several different users (with different UID's)
on the same project, but we do share the same GID.
It would be great to introduce more safe_mode file access restriction
levels, ie. a "same_group" parameter, allowing different UID's as long
as the GID's match.
/HC,
Denmark
PS: "safe_mode_exec_dir" sometimes behaves strangely when there isn't a
trailing slash.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=12872&edit=1