Bug #13818 Updated: safe mode wrong uid -1
| From: | bart at sunsite dot dk | Date: | Wed, 26 Jun 2002 08:19:51 +0000 |
| Subject: | Bug #13818 Updated: safe mode wrong uid -1 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-12109@lists.php.net to get a copy of this message | ||
ID: 13818
Updated by: bart@sunsite.dk
Reported By: ballen@umuc.edu
Status: Bogus
Bug Type: *General Issues
Operating System: solaris
PHP Version: 4.0.6
New Comment:
I get this error with php4-200206240900 / apache-2.0.39 on Solaris 8.
And yes, apache defaults to run as -1, but this has been succesfully
configured to another uid here.
Previous Comments:
------------------------------------------------------------------------
[2002-04-28 10:55:36] jflemer@php.net
The version of PHP that this bug was reported in is too old. Please
try to reproduce this bug in the latest version of PHP (available
from http://www.php.net/downloads.php
If you are still able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
I believe this has been fixed on solaris since 4.0.6.
------------------------------------------------------------------------
[2002-04-05 05:44:19] sander@php.net
I might be mistaken, but doesn't Apache try to run as -1 by default? On
some systems that refers to nobody. Might that be that case?
------------------------------------------------------------------------
[2001-10-24 13:41:52] ballen@umuc.edu
I could not find any reference on the newsgroups to the following error
we are getting when safe mode is on:
Warning: SAFE MODE Restriction in effect. The script whose uid is -1 is
not allowed to access ../orders.txt owned by uid 66400 in
/class/em680a/www/cgi-bin/vieworders.php on line 10
The "-1" can't be a uid, but I can't figure out what the error is.
There was a bug post on 12/8/2000 by someone who was getting the same
error but the uid was "1" not "-1" and the suggestion was to upgrade
php and reopen the issue if it was not fixed.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=13818&edit=1