My smb.conf is :
security = share
passdb backend = tdbsam
read only = yes
write list = share1rw
username = share1ro share1rw
valid users = share1ro share1rw
path = /var/lib/samba/shares/tmp
In this environment, share1rw can not be authorized but share1ro can.
If we remove "valid users" parameter, then share1rw can be authorized. (though, BUG#1254 still remains...)
What does "share1rw can not be authorized" mean here ? Do you mean cannot be authorized for write ?
(In reply to comment #1)
> What does "share1rw can not be authorized" mean here ?
It means that share1rw user can not access to share1.
I tested againt Samba 3.2.6 and this bug is fixed at 3.2.6. (And not at 3.2.5) .
Perhaps BUG#5927 is fixed as a part of BUG 1254: Fix "write list" in setups using "security = share".