Bug 212805

Summary: No way to add a default entry for "Others" through the ACL directory permissions dialog
Product: [I don't know] kde Reporter: Zlamma <slammer>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Zlamma 2009-11-02 21:38:58 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

Using a command line it is possible to add a default ACL entry for "others" to a directory issuing:
setfacl -m d:o:rwx dirname
but such an option does not exist in the ACL directory permissions dialog (for a directory on a filesystem mounted with acl option > directory's 'Properties' context menu option > Advanced Permissions > Add Entry...). 
The dialog there, when chosen a Default entry type, only has an option to set it  for the owner, owning group, named group, named user or setting a default mask which doesn't let one achieve the "Others" effect.

The feature is really useful when one wants to have a directory with a specific permission for 'Others' on newly created files and subdirectories in that directory, e.g. for a public folder, where everyone needs to be able to create and modify its contents even in the subdirectories created later by users.

Also, to be more specific, the 'Default for new files in this folder' option could mention that it also applies to subfolders.
Comment 1 Janek Bevendorff 2012-09-07 14:27:49 UTC
This option exists, although you can only set it implicitly.
Adding any default ACL will also automatically add an entry for Owner, Owning Group and Others (this is just how ACLs work).

But I agree that this is very counterintuitive. Managing default ACLs in general is very inconvenient with this dialog and some basic features are missing. Therefore I mark this as a duplicate of bug 122933. I hope, you agree.

*** This bug has been marked as a duplicate of bug 122933 ***