#32503 [Opn->Fbk]: fopen() in cwd: filename must start with ./ under safe mode
| From: | sniper@php.net | Date: | Mon, 04 Jul 2005 14:23:37 +0000 |
| Subject: | #32503 [Opn->Fbk]: fopen() in cwd: filename must start with ./ under safe mode | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-81374@lists.php.net to get a copy of this message | ||
ID: 32503
Updated by: sniper@php.net
Reported By: Bjorn dot Wiberg at its dot uu dot se
-Status: Open
+Status: Feedback
Bug Type: Filesystem function related
Operating System: IBM AIX 5.2.0.0 ML5
PHP Version: 5CVS-2005-07-04
New Comment:
Try the latest CVS now, the crash should be fixed in it.
(and don't invent your own version naming again)
Previous Comments:
------------------------------------------------------------------------
[2005-07-04 13:54:42] Bjorn dot Wiberg at its dot uu dot se
With this release, Apache segfaults in mpm_common if I try to access
the directory where I have enabled safe mode:
root@spinus:/# gdb /nynom/apache/bin/httpd /home/bwiberg/core
GNU gdb 5.0-aix51-020209
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "powerpc-ibm-aix5.2.0.0"...
Core was generated by `httpd'.
Program terminated with signal 11, Segmentation fault.
#0 0x10032354 in sig_coredump (sig=11) at mpm_common.c:1050
1050 mpm_common.c: No such file or directory.
(gdb) bt
#0 0x10032354 in sig_coredump (sig=11) at mpm_common.c:1050
#1 0xffffffff in ?? () from (unknown load module)
The Apache error log indicates:
[Mon Jul 04 13:51:52 2005] [notice] child pid 1654882 exit signal
Segmentation fault (11)
[Mon Jul 04 13:51:53 2005] [notice] child pid 1667296 exit signal
Segmentation fault (11)
[Mon Jul 04 13:51:53 2005] [notice] child pid 1155238 exit signal
Segmentation fault (11)
[Mon Jul 04 13:51:53 2005] [notice] child pid 290932 exit signal
Segmentation fault (11)
[Mon Jul 04 13:51:53 2005] [notice] child pid 892998 exit signal
Segmentation fault (11)
[Mon Jul 04 13:51:54 2005] [notice] child pid 1781880 exit signal
Segmentation fault (11)
This also happened with an earlier snapshot release (2005-06-21 10:30),
although I thought it would be a temporary error because of CVS
development.
Best regards,
Björn
------------------------------------------------------------------------
[2005-07-04 01:06:08] sniper@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
------------------------------------------------------------------------
[2005-05-09 14:15:53] Bjorn dot Wiberg at its dot uu dot se
Hi again!
I just tried the #define HAVE_BROKEN_GETCWD 1 trick from
http://bugs.php.net/bug.php?id=32501, with PHP
5.0.4 (the "fixed"
version) but that didn't help in this regard. I thought I would mention
this.
Best regards,
Björn
------------------------------------------------------------------------
[2005-04-05 09:28:28] Bjorn dot Wiberg at its dot uu dot se
Hi Tony!
Thank you for your feedback!
I'm afraid that absolute paths aren't a very viable solution to this,
as that probably would break too many scripts, expecting it to be
possible to "just" save a file to the current directory.
Is the "PHP realpath hack" supposed to handle these kind of problems on
AIX?
Please let me know if I can help in any way!
Best regards,
Björn
------------------------------------------------------------------------
[2005-04-04 17:11:05] tony2001@php.net
Right, this is somehow concerned with broken realpath() on AIX.
The problem is that we end up with relative path in php_checkuid_ex()
function and it fails to check permissions for the directory.
Of course, the easiest solution is to use absolute paths everywhere.
------------------------------------------------------------------------
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/32503
--
Edit this bug report at http://bugs.php.net/?id=32503&edit=1