[Bug 224317] Re: Minimal rights samba share

[Steve Langasek]

I don't believe that the uid and gid options should have any effect
here; the problem is not in the ownership of the file, but that the
permissions of the created file as shown on the client are not
consistent with the share configuration and mount options.  This
indicates that the kernel client is somehow caching what it believes the
file permissions to be, and believes them to be other than what is set
with the file_mode and dir_mode options.

This precise behavior is reproducible only when using unix extensions =
no on the server side.  On the client side, here is the minimal set of
mount options needed to reproduce:

  mount -tcifs //server/public_share /mnt/tmp -o
file_mode=0777,guest,sec=none

(Note that the lfs option is a no-op for cifs, and the codepage option
is a no-op for any server that supports Unicode.)

I'm reassigning this to the linux package, since the implementation of
cifs is in the kernel.

markba, as a workaround you can add the 'noperm' mount option to
completely bypass the buggy client permissions behavior.

** Changed in: linux (Ubuntu)
Sourcepackagename: samba => linux
   Importance: Undecided => Low
       Status: Incomplete => Confirmed

-- 
cifs: file_mode ignored when creating files on a samba server with unix extensions = no
https://bugs.launchpad.net/bugs/224317
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.