NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Hazimil
Jul 16, 2014Aspirant
Quesy regarding Network Access vs File Access
Hi All, I've now got my ReadyNAS 314, installed a single WD Red 1TB (for now), and upgrade to ReadyNAS v6.1.8. I've set-up my users, and started to work on my shares. However I confused between...
xeltros
Jul 20, 2014Apprentice
I didn't speak about windows because, with basic concepts being the same, windows handles everything at the file level way more easily than linux does for SMB. I tend to authorize everything for everyone on the share rights on windows and locking with NTFS rights (because they give more control interestingly) while I do exactly the opposite with linux. Windows being an all in one solution for SMB/CIFS shares, that's more convenient like this (and in windows server, that's how it's meant to be since share permissions hidden in a submenu and grant everyone full control).
That said when you install other more enterprise software you use a "system account" for the software and then create users inside it like for linux (Oracle server for example works like this).
Either way the least permissive of the two applies, and an explicit deny (clicking refuse, not just letting blank on windows, depends on software for linux) will result in a denied access even if the user is a member of a group that is allowed.
That said when you install other more enterprise software you use a "system account" for the software and then create users inside it like for linux (Oracle server for example works like this).
Either way the least permissive of the two applies, and an explicit deny (clicking refuse, not just letting blank on windows, depends on software for linux) will result in a denied access even if the user is a member of a group that is allowed.
netghiro
Aug 20, 2015Aspirant
Hi :)
I'm interested in your post 'cause as a newbie (in both NAS and LINUX) file permissions are crucial (see my post here).
I don't have a Linux background (unfortunately) so something that I say may sounds silly because of that.
So.. in your first post you say "the weakest on the two sets of rights applies" but after, in the next post, you say "Either way the least permissive of the two applies" (which means strongest, the opposite).
Also for me english is not my first language so I possibly have misunderstood something :)
Many thanks
- StephenBAug 20, 2015Guru - Experienced User
netghiro wrote:
So.. in your first post you say "the weakest on the two sets of rights applies" but after, in the next post, you say "Either way the least permissive of the two applies" (which means strongest, the opposite).
"Least permissive" is correct, and results in the most restrictive policy.. Personally I wouldn't use strong/weak to describe this. Strong implies inherently better (there is no value in weak encryption, unless you are wanting to do mass surveillance). However, more restrictive is not inherently better than less restrictive, and there are use cases where less restrictive is what you need.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!