ID:               22454
 Updated by:       [EMAIL PROTECTED]
 Reported By:      gpt at tirloni dot org
-Status:           Open
+Status:           Bogus
 Bug Type:         *General Issues
 Operating System: FreeBSD 4.7-p3
 PHP Version:      4.3.1
 New Comment:

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.

See bug #20195



Previous Comments:
------------------------------------------------------------------------

[2003-02-27 08:59:51] gpt at tirloni dot org

I just installed /usr/ports/www/mod_php4 version 4.3.1 on a FreeBSD
4.7-RELEASE-p3 that didn't have php previously installed and it
installed the world-writeable files again.

The umask was 022 and the ports collection was updated before the make
install from cvsup9.FreeBSD.ORG. The apache used this time was 2.0.44
(it that matters), others were 1.3.27.

------------------------------------------------------------------------

[2003-02-27 08:48:02] gpt at tirloni dot org

umask 022

------------------------------------------------------------------------

[2003-02-27 08:45:11] [EMAIL PROTECTED]

What was your umask set to when you ran make install?

------------------------------------------------------------------------

[2003-02-27 07:26:21] gpt at tirloni dot org

# find /usr/local/lib -perm -0002

------------------------------------------------------------------------

[2003-02-27 06:46:14] gpt at tirloni dot org

 I installed php 4.3.0 from the FreeBSD's ports collection and it
installed some files in /usr/local/lib/php with world-writeable
permissions. After updating to 4.3.1 the problem persisted and a friend
of mine ([EMAIL PROTECTED]) also reported that he installed
4.3.0 by hand on FreeBSD and it also had the world-writeable files in
/usr/local/lib/php.

 Version 4.2.3 of PHP on a FreeBSD 4.6.2 didn't show this problem and I
didn't try to update it to 4.3.1 yet.

 Sorry but I don't have a Linux system right now to update to 4.3.1 and
see if the problem persists. At first I thought it was a FreeBSD port's
problem but installing it manually didn't help so the port's system
isn't involved in this (I guess).

------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=22454&edit=1

Reply via email to