ID: 20195
Comment by: gpt at tirloni dot org
Reported By: cycloon at linux-de dot org
Status: Open
Bug Type: *General Issues
Operating System: linux
PHP Version: 4.3.2-dev
New Comment:
Hi,
I'm having the same problem. If you want to have more details please
see bug report #22454.
Was it fixed or will it be fixed for 4.3.2?
Thanks in advance
Previous Comments:
------------------------------------------------------------------------
[2003-01-03 18:18:53] cycloon at linux-de dot org
no, i changed my umask for root back to 022, since some other apps had
the same problems, but i still think, that we should use "install" to
copy the files
------------------------------------------------------------------------
[2003-01-03 17:37:21] [EMAIL PROTECTED]
Do you still experiment the problem with PHP 4.3.0 ?
(can you verify the permission of pear in /usr/local/bin/pear by
default too? )
Thank you for your report.
------------------------------------------------------------------------
[2002-11-04 00:09:35] cycloon at linux-de dot org
no comments anymore, sniper?
------------------------------------------------------------------------
[2002-10-31 14:23:54] cycloon at linux-de dot org
POSTs are infected as the php binary is created correctly (gcc gives it
the right permission) but include files and other folders have wrong
permissions, so POSTs dont work.
Using the "install" programm with its arguments to set permissions,
owner and group would solve this problem.
------------------------------------------------------------------------
[2002-10-31 13:51:46] cycloon at linux-de dot org
Hardly every files are installed incorrectly, even directories are not
set to 755. Normally "make install" uses "install" i think (apache does
so) and they use the options -g, -m and -o to set group, mode and owner
of the files, php does not, it just creates the files and this normaly
uses the permission a user set with 'umask' like you create a file with
touch or so.
------------------------------------------------------------------------
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/20195
--
Edit this bug report at http://bugs.php.net/?id=20195&edit=1
