Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > Tips/Tricks/Mods

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Thread Tools Display Modes
Prev Previous Post   Next Post Next
Old 7th March 2010, 02:12
ethanlifka ethanlifka is offline
Junior Member
Join Date: Aug 2008
Posts: 29
Thanks: 0
Thanked 6 Times in 4 Posts
Default SuPHP move_uploaded_file fileperms to 600 instead of 644

Its your /tmp directories - More info below

It seems that when you use move_uploaded_file() with SuPHP or FastCGI with SuExec the File Permissions are being set to 600 instead of 644.

This means any readable files like images, text, etc or not accessable by http. You need at least 640 to have be accessable by http.

At first everyone said it can be set in /etc/suphp.conf.
Change umask to 0022 instead of 0077.
Then restart apache.

FYI, if you are using FastCGI with suExec you can set umask in your sites ".php-fcgi-starter" file by adding "umask 0022"
umask 0022
export PHPRC
NOTE: You can also edit "/usr/local/ispconfig/server/conf/php-fcgi-starter.master", but be asure to edit it directly and not FTP. Editing master files with FTP may result in PHP Parsing Errors.

Well my umask was already 0022. So this was not the solution for me.
Then everyone said just use chmod() after move_uploaded_file(). Which works great, but is not a good solution for big hosting companies who want to easily migrate multiple sites to their server. Having to change so much php code can be overwhelming.

After more research I found that it is not suphp.conf because the umask setting does work. Try mkdir() or fwrite(). Files and directories are set to 755 and 644 just fine. It's not the move_uploaded_file() function either.

It's your /tmp directories. Any files created in them are set to 600. The HTTP FILES Upload uses your sites /tmp to upload the file to. Not sure where the source of this 600 fileperms setting is coming from. Maybe your OS, maybe suPHP or suExec core.

If you know then please respond !!!!!!

I believe it is a security feature to not have any files in /tmp readable, writable, or executable by anyone other then the owner.

So when you use move_upload_file() it keeps the fileperms that where originaly set by the /tmp directory or your sites /var/www/site.com/tmp directory.

if you use copy() instead of move_uploaded_file() then it will generate 644 instead of 600.

Hope this helps.

I am still looking for a solution to automaticly set files to 644 with and only using move_uploaded_file().

Is it possable to rewrite the move_uploaded_file() function or append the chmod() after it?

Last edited by ethanlifka; 7th March 2010 at 02:21.
Reply With Quote
Sponsored Links


600, move_uploaded_file, suphp

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
suPHP file permission catalyst General 14 7th March 2010 02:16
Security - mod_php with FTP vs SuPHP or SuExec ethanlifka Installation/Configuration 1 22nd February 2010 11:18
Goal: user separation (but apache can't read what suPHP wrote) berny Installation/Configuration 1 26th April 2008 19:22
Please Help me SmartAX MT810 :( cola Technical 0 9th November 2007 12:50
Fedora Core 6 install issues moos3 Installation/Configuration 10 22nd March 2007 19:25

All times are GMT +2. The time now is 02:11.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.