Samba's "read list" and "write list" configuration directives

The manpage description of "read list" and "write list" might be a little bit confusing to a Samba-newbie like me. Smile I thought that to restrict users I just had to set "read list" to an empty value and "write list" to a set of users+groups. However these do not work as I thought.

O'Reilly has a nice guide to Samba and they explain it more clearly: "These options can be used on a per-share basis to restrict a writable share or grant write access to specific users in a read-only share, respectively."

So neither of these does affect whether a user can access a share or not. For that you have to use the "valid users" directive.

Eg. if you want a share to be accessible by users of group1 and group2, but allow write only to members of group2, then you have to use the following directives for the share:
valid users = @group1, @group2
read only = yes
write list = @group2

PS: of course you have to keep in mind that the rules in smb.conf do not override the OS-level permission rules. Eg. if you want to give access to a share to two groups, then you have to give world-wide access to the directory of that share since the directory on the OS-level can belong only to one group. Or you could use OS-level ACLs, but this is not very common in the linux world.

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

have you try it?

this feature does not work for me and many admin.

in http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
section "write list (S)" states:

"By design, this parameter will not work with the security = share in Samba 3.0."

Re: have you try it?

I've never used "share" level security, thus I don't know much about it. But if the docs say write list won't work with security = share, then it's probably the reason why it does not work for you either.