Automatically inherit 755 permissions inside public_html folder
When creating new users in Ubuntu, their home directory is created with a "public_html" folder. The permissions for this folder are 755. However, any files or folders I ftp to public_html inherit 600 (file level) or 700 (folder level). I can manually change these permissions using the FTP client, command line, or webmin ---- but it would be handy if all new files and folders inherited 755 permissions.
ASKER
Getting a message at the terminal, "operation not permitted"
Ok, its basic, but you did this as a root/admin?
What operation did you do that was not permitted?
In this forum since you are the eyes and hands, you need to provide as much detail as possible as to what you did and what you saw for me to be able to understand the situation and possibly suggest a course of action to achieve your goal.
In this forum since you are the eyes and hands, you need to provide as much detail as possible as to what you did and what you saw for me to be able to understand the situation and possibly suggest a course of action to achieve your goal.
ASKER
Not as root, but as an admin. Should I attempt it as root?
I performed the below operation
chmod 755 /etc/skel/public_html
I performed the below operation
chmod 755 /etc/skel/public_html
ASKER
Logging in as root allowed the operation.
I deleted and readded the user. Public_html folder created automatically with 755 permissions, but again, when I transfer folders or files via ftp, they inherit rw permissions only.
I deleted and readded the user. Public_html folder created automatically with 755 permissions, but again, when I transfer folders or files via ftp, they inherit rw permissions only.
Within the FTP configuration, make sure the umask is set to 022 and not 077.
Which ftp server do you use vsftp, wsftp, proftpd etc.
/etc/<yourftpserver_type>/
some use the local_umask= as the means to control the creation of files/directories by users and should be set to 022.
If you are using a GUI based FTP client, it often has the option to change the settings(chmod).
on the command lite you have to issue the quote site chmod 755 for each directory and 644 for each file.
Which ftp server do you use vsftp, wsftp, proftpd etc.
/etc/<yourftpserver_type>/
some use the local_umask= as the means to control the creation of files/directories by users and should be set to 022.
If you are using a GUI based FTP client, it often has the option to change the settings(chmod).
on the command lite you have to issue the quote site chmod 755 for each directory and 644 for each file.
after you make the configuration, restart the ftpd service.
ASKER
ProFTPD
Here is the config file:
# # <Directory incoming>
# # # Umask 022 is a good standard umask to prevent new files and dirs
# # # (second parm) from being group and world writable.
# # Umask 022 022
# # <Limit READ WRITE>
# # DenyAll
# # </Limit>
# # <Limit STOR>
# # AllowAll
# # </Limit>
# # </Directory>
Are you saying to uncomment the Umask?
Here is the config file:
# # <Directory incoming>
# # # Umask 022 is a good standard umask to prevent new files and dirs
# # # (second parm) from being group and world writable.
# # Umask 022 022
# # <Limit READ WRITE>
# # DenyAll
# # </Limit>
# # <Limit STOR>
# # AllowAll
# # </Limit>
# # </Directory>
Are you saying to uncomment the Umask?
Yes, or make sure there is nothing else that sets the UMAS to 077 either in the startup scripts, etc. Since looking could take a long time, setting it explicitly here should resolve the issue without the need to track.
ASKER
New files transferred are being assigned 644. They're missing the execute portion to make them 755. I was reading up on ProFTPD and found that it might not be possible to automatically assign execute rights to new files (only to folders) - that these rights had to be taken care of via the console or gui. If that's the case, I'll deal with it. But I was looking for a cleaner solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, I see. And it's working. I think you've solved my problem. Thank you for the advice and patience.
ASKER
Patient and helpful
The settign for newly created files/folders is via umask such that if you have your umask set to 077 any file the user creates will be 0600 or for directory 0700
set umask to 022 and any file the user creates will have the 644 or 755 right for file/directory respectively.
The ftp server is often/commonly defaults to umask of 022
umask is a negative/reverse mechanism i.e. when a file is created the permissions are set based on the umask starting with 777 and then negated by the setting in the umask in this case the write right is removed from the group and world.
Hope this clarifies it. another option if you have a centrall login script, you can add within it a process that on user login/logout goes through that user's public_html folder and resets the permissions on the subdirectories and sub files to 755,644 respectively. You may want to take a consideration that a user may have set their directory to 711 to avoid having that directories contents from being browsable. And the auto-change setting suggested above will reverse that decision by the user. So checking for the current mod of the directory should be considered.