You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition to the standard rwx bits for files, most Unix systems now also support extended ACLs to provide finer granularity over filesystem permissions.
One of the options provided by ACLs is the ability to set default permissions for all files and folders under a given path.
I have set up my ubuntu-10.04 server with a default ACL which should result in all files saved under the path to have the permissions rw-rw-r-- (664).
Other ftp clients, such as Filezilla, Transmit, and Fetch, properly create files that obey this default ACL. WinSCP does as well.
Cyberduck, however, does not obey the default ACL, even when "change permissions" is unchecked for file uploads.
The text was updated successfully, but these errors were encountered:
When Change Permissions is unchecked for uploads, the permission bits are not set for the file created on the remote host via SFTP therefore the default ACLs should apply. I cannot replicate this issue.
In addition to the standard rwx bits for files, most Unix systems now also support extended ACLs to provide finer granularity over filesystem permissions.
One of the options provided by ACLs is the ability to set default permissions for all files and folders under a given path.
I have set up my ubuntu-10.04 server with a default ACL which should result in all files saved under the path to have the permissions
rw-rw-r-- (664)
.Other ftp clients, such as Filezilla, Transmit, and Fetch, properly create files that obey this default ACL. WinSCP does as well.
Cyberduck, however, does not obey the default ACL, even when "change permissions" is unchecked for file uploads.
The text was updated successfully, but these errors were encountered: