[Samba] File permissions change after implementing vfs_fruit

[tackyy]

Hi,

I previously had an issue that was fixed by implementing vfs_fruit. For reference: https://lists.samba.org/archive/samba/2016-April/199583.html <https://lists.samba.org/archive/samba/2016-April/199583.html>

I’m running Samba 4.2.11 on FreeBSD 10.0 release and our shares are on ZFS. Our macs are on OS X 10.11.4.

What I had previously was this:

vfs objects = zfsacl

Which I then changed to this:

vfs objects = zfsacl catia fruit streams_xattr
fruit:resource = xattr
fruit:metadata = stream

That seems to have fixed my old issue. But the new issue that popped up is when users upload, create or modify a file on the server, the permissions change. Like they would go from -rwxrwx---+ to  ----rwxr--+ This is undesirable because when another user tries to then download the file then open the local copy, they get denied access.

First thing I tried was commenting out the fruit xattr settings after seeing some threads stating it was only really supported on Solaris:

vfs objects = zfsacl catia fruit streams_xattr
#fruit:resource = xattr
#fruit:metadata = stream

That seems to have made no difference. I then changed the create mode in a share I was testing on

from:
create mode = 0660
to:
force create mode = 0760

That had the effect of instead of making files --rwx--+ they’d come up as -r--rwxr--+.

What am I missing here? Would fruit:nfs_aces = no be the way forward? Is the order I list my vfs objects in problematic? 

Cheers,
tack