I have recently encountered a problem in Samba 3.0.4 that ignores the "write list" parameter when "security" parameter is set to share. Below is the example of smb.conf to reproduce the situation. In this example, I have used user shiro:shiro for accessing the share tmp. [global] security = share guest ok = yes [tmp] path = /tmp writeable = no guest ok = no write list = @shiro In Samba 3.0.2a, it allows write access to user shiro on share "tmp", whereas in Samba 3.0.4 it does not permit writing any data onto the share. If I change the security mode to "user", Samba grants write access to the user shiro. I had a quick glance at the CVS tree and realised that between the revisions 1.122.2.8 and 1.122.2.9 of smbd/service.c, set_read_only() function had been removed and the whole procedures had been migrated to is_share_read_only() function in smbd/uid.c. What I'd like to know is whether this change of behaviour is intentional or not, in other words do you classify it as a bug?
this should be fixed in post 3.0.4 releases. If you still encounter the problem with 3.0.5 please reopen this bug.
(In reply to comment #1) > this should be fixed in post 3.0.4 releases. If you still encounter the problem > with 3.0.5 please reopen this bug. Do you mean it should be fixed in 3.0.5rc1? If that is so, then I must disappoint you to say that I have managed to reproduce it in 3.0.5rc1. I'm not sure about HEAD cvs tree, as I failed to build binaries from it.
I've managed to reproduce it from the binaries built from the source code in subversion (Rev. 1556). I am going to reopen this issue.
*** This bug has been marked as a duplicate of 1254 ***
originally against 3.0.5rc1 (which was 34.0.6rc1 due to the security release).