#SAMBA SHARE ENGINEERING GROUP FULL#

The other SMB user could not even see that file now! I then checked with Windows Explorer from smb_one, and it was allowed to read and change the ACLs of the file and initially set them to 'only I am allowed to do anything with it'. I now logged in via SMB ( smb_one) and let Winword save a file. They still are all members in the auxiliary smb_users group (GID=Auto, Sudo=No, SambaAuth=Yes). The users still are smb_one, smb_two and so on (currently just testing, as you might imagine).

With the help from anodos, I've now come up with another setup: When I go to the shell and do getfacl my_file.txt, I get this: The intention of that ACL is: Everybody from the smb_users group shall be able to read and write at the share, but may not start messing around whith ACLs.īut something seems to be wrong with it – when smb_one creates a file (or directory), smb_two can read the file and the directory and he/she can delete both – but he/she cannot modify the file! I have all the users in a 'sambashare' unix group and want to offer the directory /data/shared to all members of the 'sambashare' group for read and write access. I'm trying to set up a samba share where everyone has read and write access. Group smb_users - Allow - Advanced - Basic Flags - Inherit I have an Ubuntu server in my house running samba.

Owner: - Allow - Basic - Full Control - Basic Flags - Allow - Basic - Full Control - Basic Flags - Inherit

The Share has the following filesystem ACL: They are all members in the auxiliary smb_users group (GID=Auto, Sudo=No, SambaAuth=Yes). The users are smb_one, smb_two and so on (currently just testing, as you might imagine). On my TrueNAS Core, I have an SMB share I want to give access to a group of users in order to let them share files. I am having this strange-looking '?' floating above my head that only true misunderstanding of Samba permissions can produce – maybe you can help me changing it to '!'?

#SAMBA SHARE ENGINEERING GROUP FULL#

Samba share engineering group