Samba 3.0.20 read-only behaviour

[Andrew Bartlett]

I'm still not convinced that the behaviour in Samba 3.0.20 is correct
for setting the read-only dos attribute on files.

In particular, I don't see why a share being read only, or a file being
read only to the current user on the remote server should set the DOS
attribute of read only.  I certainly understand for the NTcreate
disposition stuff, where we are returning 'can you do this', but the DOS
attribute has a completely different meaning, and a nasty habit of being
copied around.  

I also have seen a nasty bug where a directory with GID access
permission (with a gid rws permission) is 'read only' on the client.  I
need to chase this down outside my production environment, I'll get more
details later.

Andrew Bartlett
-- 
Andrew Bartlett                                http://samba.org/~abartlet/
Samba Developer, SuSE Labs, Novell Inc.        http://suse.de
Authentication Developer, Samba Team           http://samba.org
Student Network Administrator, Hawker College  http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba-technical/attachments/20051011/c6c4f0cd/attachment.bin