NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
chopin70
Nov 12, 2020Virtuoso
Shares user and and group permissions
Hi, 4 years after this thread... https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/User-and-group-broken-permissions/td-p/1107451/page/3 I am migrating to FreeNAS and turni...
StephenB
Nov 15, 2020Guru - Experienced User
FWIW, when I set file permissions so that the group smb_enfants_ro is read-only in the GUI, I also end up with read-only access for enfants2. I did not set any permissions for enfants. I confirmed first that with network access also set with the group having only read access - and then confirmed it again with network access giving everyone rw access.
The linux ACL for the each file in the folder looks like this:
root@NAS:/data/enfants2# getfacl * # file: FileAccess.png # owner: admin # group: admin user::rwx user:admin:rwx user:guest:rwx group::rwx group:admin:rwx group:guest:rwx group:smb_enfants_ro:r-x mask::rwx other::---
This file was copied into the share from windows previously with admin credentials.
The linux ACL for the share itself looks like this:
root@NAS:/data/enfants2# getfacl . # file: . # owner: guest # group: guest user::rwx user:admin:rwx user:guest:rwx group::rwx group:admin:rwx group:guest:rwx group:smb_enfants_ro:r-x mask::rwx other::--- default:user::rwx default:user:admin:rwx default:user:guest:rwx default:group::rwx default:group:admin:rwx default:group:guest:rwx default:group:smb_enfants_ro:r-x default:mask::rwx default:other::---
The share is owned by guest/guest, and folder group and folder owner both are set to rw access.
Note I did not attempt to apply file permissions from Windows - I set them for the share using the web ui.
chopin70 wrote:
Any Netgear tech we can ping ?
chopin70
Nov 16, 2020Virtuoso
Wired,
In my case and above test, the File Permissions applied only at group level in the GUI did not propagate to the users in linux shell mode.
Furthermore, changing File Permissions in GUI did not propagate them to the ACLS. It is rather the "Network TAB" in my case that did propagate the ACLS permissions to Windows 10 ACLS.
As shown in my above screeshots, the user teddy still got r/w permissions and could delete tommy's owned folder at the root of the freshly created office share which is just amazing and should never happen as far as I know.
Anyway, maybe there is an inconsitent bug in GUI that causes this ?
My advise is to ensure all permissions are properly propagated to windows 10 ACLS. Once verified, to only apply them from windows 10 and to verify that they properly apply to the shell access, either you are using it or not for security reasons.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!