[wp-trac] [WordPress Trac] #9811: ftp for plugin update fails to set correct privileges if umask not 0022

[WordPress Trac]

#9811: ftp for plugin update fails to set correct privileges if umask not 0022
--------------------------+-------------------------------------------------
 Reporter:  lovingboth    |       Owner:                                 
     Type:  defect (bug)  |      Status:  new                            
 Priority:  normal        |   Milestone:  Unassigned                     
Component:  Plugins       |     Version:  2.7.1                          
 Severity:  normal        |    Keywords:  plugin update permissions umask
--------------------------+-------------------------------------------------
 If the ftp user's umask is not 0022, newly created directories and files
 may not be read-enabled for other users, such as the webserver.

 Having umask 0022 is the default for many, but not all, ftp servers.
 vsftpd has a default of 0077, for example. This results in new files not
 being readable by anyone other than the user, and so if the webserver is
 running as its own/another user, WP cannot see them.

 Possible solutions:

 1. WP should check umask, and change if necessary, prior to creating them.

 2. WP should chmod newly created files/directories to the prvileges it
 expects.

 3. WP should check privileges on newly created files/directories, and
 report a failure if they are not what it expects.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9811>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software