ID: 37236 User updated by: youza at post dot cz Reported By: youza at post dot cz -Status: Closed +Status: Open Bug Type: *Directory/Filesystem functions Operating System: fedora core 4 PHP Version: 5.1.4, 4.4.2 New Comment:
Hello, please i cannot find the fix in 4.4.4 CVS, please help me. Is this bug fixed in the 4.4.4(5) CVS ? Sorry if my question is irrelevant. Previous Comments: ------------------------------------------------------------------------ [2006-10-23 07:49:30] youza at post dot cz Sorry, I cannot find this fix in CVS for 4.4.4 ? ------------------------------------------------------------------------ [2006-10-23 07:46:41] youza at post dot cz I can find this fix in CVS for 4.4.4 ? ------------------------------------------------------------------------ [2006-10-16 15:12:27] [EMAIL PROTECTED] This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2006-08-04 07:36:42] youza at post dot cz Other details: if upload_tmp_dir is on a different filesystem then the destination file, the function move_uploaded_file (for PHP 4.4.2) - work fine and the destination file has permission -rw-rw-r-- UID/GID apache/apache ( apache process started witch umask 0002 ). But upload_tmp_dir is on a the same filesystem then the destination file, permission for new destination file is -rw------- UID/GID apache/apache !!!! ( tested PHP 4.4.2, PHP 5.1.4 ) The permissions is incorrect users in apache group will not have access to this files. Diferent permission depending to the upload_tmp_dir and filesystem location not correct. ------------------------------------------------------------------------ [2006-07-23 12:27:59] [EMAIL PROTECTED] Sara, anything new about this? ------------------------------------------------------------------------ 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/37236 -- Edit this bug report at http://bugs.php.net/?id=37236&edit=1
