Permission problem in xml-upload?

[Nemesis666]

I can't trace it down, but I found out the following issue in 1.0 beta 4 when uploading a module via xml (tried captcha and another I don't remember):
After uploading the xml-file, all files and directories, that were created are chmod 366, so that the world can't read them! That's really crazy, because right after installation the module manager can't access the module and displays access-errors.

I checked, wheter it was a problem of my webhoster, but with a simple php file, that created a file, wrote a line and closed it thereafter produced a file with permissions 644. So it's not a problem of the webserver.

Anybody any ideas?

Regards,
Nemesis

[Nemesis666]

Ok, found the problem myself: In admin-setting umask is used instead of chmod, which work inverse to each other. So I put in a 777 and (weird enough) it produced a 366 instead of 000. So I have to put a 000 to get a 777, or a 022 to get 755.

Crazy. Why not use chmod, as it set permissions like the unix style command. Does the permission setting in config also use umask, or does this one use chmod???

Thanks for the response,
Nemesis