Thread: Secure Shared Hosting ... A Paradox?

But if a shared user sets file permissions to 644 and 755 for their files/folders how would that work? Is there a way to make open_basedir apply for ANY file/folder in a users home directory so that User A's files BOTH php and non-php, no matter what permissions are set, can't be viewed by User B (by SSH, FTP, PHP include or any other type access)? According to what I hear the only solution to protect users and still have their files...

If you looking about 640 permissions try to google about umask. Do not forget to apply it to ftp server. It easy to set up proper permissions. Just set 750 for every dir in /home and add apache/nobody user to every group. Sure you need to use suphp or fastcgi to prevent scripts run as apache/nobody. With this 640 permissions and open_basedir not really necessary.

But if a shared user sets file permissions to 644 and 755 for their files/folders how would that work? Is there a way to make open_basedir apply for ANY file/folder in a users home directory so that User A's files BOTH php and non-php, no matter what permissions are set, can't be viewed by User B (by SSH, FTP, PHP include or any other type access)? According to what I hear the only solution to protect users and still have their files...

But if a shared user sets file permissions to 644 and 755 for their files/folders how would that work? Is there a way to make open_basedir apply for ANY file/folder in a users home directory so that User A's files BOTH php and non-php, no matter what permissions are set, can't be viewed by User B (by SSH, FTP, PHP include or any other type access)? According to what I hear the only solution to protect users and still have their files...