ACL: Difference between revisions
m (Michael Murtaugh moved page Permissions to ACL: Maybe using command names makes more sense) |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
* Make sure all users are in group users with, for instance for user michael: | |||
sudo adduser michael users | |||
Access Control Lists | |||
An extension to standard UNIX-style file system permissions. | |||
== Using ACL to make an actually useable shared folder == | == Using ACL to make an actually useable shared folder == | ||
| Line 11: | Line 18: | ||
=== Links === | === Links === | ||
* [http://bencane.com/2012/05/27/acl-using-access-control-lists-on-linux/ ACL: Using Access Control Lists on Linux] | * [http://bencane.com/2012/05/27/acl-using-access-control-lists-on-linux/ ACL: Using Access Control Lists on Linux] | ||
[[Category:Protocol]] | |||
Latest revision as of 15:17, 26 September 2023
- Make sure all users are in group users with, for instance for user michael:
sudo adduser michael users
Access Control Lists
An extension to standard UNIX-style file system permissions.
Sadly the built in UNIX way of doing permissions, with it's notions of users, groups, and "others" is in practice quite difficult to use to make "shared folders". ACL (for access control lists) is an extension to these mechanisms that gives more flexibility. The setfacl command is the thing that sets the options.
So, the command to Allow anyone in the users group to write files to path/to/some/folder
setfacl -Rm g:users:rwX /path/to/some/folder setfacl -d -Rm g:users:rwX /path/to/some/folder