Hi Eminos

I did some researches about this problem. The umask is set correct: 0022 but it seems that php does not set (or removes) any group and world permissions - so there's a 0077 umask hidden in the php code - or it's somewhere else - I didn't found the hideout...

I also did some tests - one on a not very old ispcp server (just a move_uploaded_file) and the same on my 2 year old suse 10 server (with mod_php, no susexec, no fastcgi). They both have 0600 permissions on a newly uploaded files.

Well, of course with mod_php apache is able to read the files (owner = apache) which is not the case with ispcp/fastcgi/suexec - there you have to chmod the newly uploaded file.

I dug deeper: the temporary file already has the 0600 permissions set.

BUT: Now I got something very strange:
If I set the upload_tmp_dir to /tmp (with open_basedir adapted) then the file *there* also has 0600 permission mode but after the use of move_uploaded_file the files has 0644 mode (on the ispcp machine).

Very strange.

So, as a temporary solution I can give you an advice: use /tmp as upload_dir for the Joomla Customers.

And hey: Typo3 does correct the permissions after an upload :-)


Maybe someone else can have a look at this behaviour of php (raphael... ???)

Have a good sunday
Joximu

Just one more thing:

If the upload_tmp_dir is on the same filesystem as the upload-folder (normally the webspace) then the uploaded file has 0600 rights (-rw-------). If it's on a different filesystem then it has 0644 (-rw-r--r--) ... (or sth else if the umask is not 0022)...

Seems to be a PHP bug.

Conclusion for ispcp:
put the upload dir for problematic domains to another perition on the harddisc.

/J

2. Edit: Further infos see php bug
http://bugs.php.net/bug.php?id=42291

Hi,

it would be the best if everyone can "vote" for this bug. Currently it affects all php version and it is under ispCP a real problem. You can find the vote under the bug report (http://bugs.php.net/bug.php?id=42291).

Good idea!
Done - hope this will corrected very fast...

Greez BeNe

just voted...

Hi,

the PHP Team made some changes regarding this bug. But they need some help. I have currently no pc so it's impossible for me.

Someone should test the php version posted in http://bugs.php.net/bug.php?id=42291 and change the bug back to "open".

sourceforge has problems with their dolwnloads... still waiting