Thomas Mueller wrote: > Hello, > > we used to have a directory with this ACL entry > > system:authuser li > > so that users with a valid token may drop their files here, but no-one > will be able to read, modify, delete or overwrite existing files. > With the 1.4 clients this works fine. > > Now I found that the 1.5.18 client (on Windows - no other versions > checked) requires that the "w" permission must also be set to insert new > files - but this allows the modification of existing files too. > > Are my observations correct? > If so, was it intended and why? > > Thomas.
1.5.x obtains locks from the file servers whereas 1.4.x did not. The 'l' permission controls read locks not write locks. Write locks are controlled by the 'w' permission or the 'i' permission of the client owns the file. The behavior is not intended. If it is the case, please file a bug report to [EMAIL PROTECTED] Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
