Buffalo Forums

Products => Storage => Topic started by: AIffland on January 20, 2010, 06:36:40 AM

Title: User rights
Post by: AIffland on January 20, 2010, 06:36:40 AM
   

Hi,

 

is it true that Buffalo NAS (TS-RHTGL/R5 F/W 1.33, AD integrated) checks the user rights from bottom (read only) to the top (read/write)?

 

If so, why?

Normally i have a group with all users that are allowed to access (read) certain files. Then i define the group with those user that have more rights, but i don't have to delete them from the first group.

With the above NAS, i have to define a new group with all those user that should not have write access. This differs from windows behaviour.

 

Could you please confirm and comment.

 

Best regards,

 

Arnd

Title: Re: User rights
Post by: AIffland on January 22, 2010, 03:18:46 AM
   

No comments on this?

Title: Re: User rights
Post by: Colin137 on January 23, 2010, 10:46:14 AM

The Windows platforms that you're used to are using what's called "least restrictive" permissions. The Linux-based Buffalo NAS devices use "most restrictive" permissions. I'm not about to start an argument about which one's more secure, so I'll just leave it at that.

 

"Least restrictive" vs. "most restrictive" permissions is an old debate going back a while, and there's not really a consensus on what's better.

Title: Re: User rights
Post by: AIffland on January 25, 2010, 10:18:09 AM
   

Thanks.

 

So the mix of Windows (AD integration) and Linux is the problem?

It's just, when i have an option for AD integration, i just suspect that the user groups will work the same as on the base (windows) system. For this, it don't matter which system is more secure or better. But when i use windows user groups on a NAS that is working complete different regarding user rights, i have a big problem with my group definitions.

Browser ID: smf (is_webkit)
Templates: 1: Printpage (default).
Sub templates: 4: init, print_above, main, print_below.
Language files: 1: index+Modifications.english (default).
Style sheets: 0: .
Hooks called: 60 (show)
Files included: 27 - 1055KB. (show)
Memory used: 736KB.
Tokens: post-login.
Queries used: 12.

[Show Queries]