search for: nfs4acl

Hi All I found there is one bug in the plugin. The name of the attribute for ACL as per strace output of nfs4_setfacl is *system.nfs4_acl.* The source code has defined it as #define NFS4ACL_XATTR_NAME ( "system.nfs4acl" ) Note there is missing underscore. After this, the EOPNOTSUPP error is not observed. Hope this helps Akash On Thu, Apr 5, 2018 at 11:43 PM, Jeremy Allison <jra at samba.org> wrote: > On Thu, Apr 05, 2018 at 04:09:26PM +0530, Akash Jain vi...

On Fri, Apr 06, 2018 at 01:44:50PM +0530, Akash Jain wrote: > Hi All > > I found there is one bug in the plugin. The name of the attribute for ACL as > per strace output of nfs4_setfacl is system.nfs4_acl. > The source code has defined it as > #define NFS4ACL_XATTR_NAME      ( "system.nfs4acl" ) > > Note there is missing underscore. > > After this, the EOPNOTSUPP error is not observed. > > Hope this helps Hmmm. This has been changed for Samba 4.8.0 and above, with commit df99ac27106dededcf0a98a251e58c24b90bf6d1. This wou...

...his the machine that you cannot set the permissions on ? > Yes. > > >If so, what is the filesystem ? > Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS > on this last filesystem (/dev/vdb1). > If zfs is involved in any way, you will have problems, zfs uses nfs4acls, you could try adding 'nfs4acl_xattr' to the 'vfs objects' line. Rowland

...d everything" ACL in the get_nt_acl call. > It would of course be much better to get a proper mapping. What do > your ACLs look like? > Thanks for clarifying. We use NFSv4 compliant ACLs that can be accessed via the nfs4-acl-tools. I found the existing NFSv4 ACL VFS module in Samba (nfs4acl_xattr), which seems to be build on a different implementation. The referenced website ( http://www.suse.de/~agruen/nfs4acl/) does not exist anymore and the xattr to access ACLs is different (system.nfs4acl for nfs4acl_xattr and system.nfs4_acl for nfs4-acl-tools). Is this a known issue? Kind regar...

...n Fri, Apr 06, 2018 at 01:44:50PM +0530, Akash Jain wrote: > > Hi All > > > > I found there is one bug in the plugin. The name of the attribute for ACL as > > per strace output of nfs4_setfacl is system.nfs4_acl. > > The source code has defined it as > > #define NFS4ACL_XATTR_NAME      ( "system.nfs4acl" ) > > > > Note there is missing underscore. > > > > After this, the EOPNOTSUPP error is not observed. > > > > Hope this helps > > Hmmm. This has been changed for Samba 4.8.0 and above, > with commit df99ac...

...> > It would of course be much better to get a proper mapping. What do > > your ACLs look like? > > > > Thanks for clarifying. We use NFSv4 compliant ACLs that can be > accessed via > the nfs4-acl-tools. > > I found the existing NFSv4 ACL VFS module in Samba (nfs4acl_xattr), > which > seems to be build on a different implementation. The referenced > website ( > http://www.suse.de/~agruen/nfs4acl/) does not exist anymore and the > xattr > to access ACLs is different (system.nfs4acl for nfs4acl_xattr and > system.nfs4_acl for nfs4-acl-tools)....

Does anyone know how to get vfs modules - specifically zfsacl and/or nfs4acl - with samba? When I didn’t find it in 16.04, 18.04 or 19.04 ubuntu versions I decided to look elsewhere - Launchpad - but it wasn’t in that build either. So I decided to build from source thinking that there must be an option for it during build time but the Samba build options page lists no such...

Hi, the man page states For systems that support extended-attribute namespaces, a copy being done by a super-user copies all namespaces except system.*. That's the reason why NFAv4 ACLs are not copied as they are in the system.nfs4_acl (or system.nfs4acl) namespace. Why are those namespaces excluded? Not being able rsync ACLs von NFSv4 is a major drawback now that NFsv4 becomes standard oder v3 and ACLs are getting more widely used. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik...

I am looking for where zfsacl settings such as, zfsacl: acesort = dontcare , are documented. Do I need NFS settings such as, nfs4: mode = simple , if I am not using NFS? If I do, where are they documented? Thanks

...gt; > > > Hi All > > > > > > > > I found there is one bug in the plugin. The name of the attribute for ACL as > > > > per strace output of nfs4_setfacl is system.nfs4_acl. > > > > The source code has defined it as > > > > #define NFS4ACL_XATTR_NAME      ( "system.nfs4acl" ) > > > > > > > > Note there is missing underscore. > > > > > > > > After this, the EOPNOTSUPP error is not observed. > > > > > > > > Hope this helps > > > > > &gt...

...;> Yes. >>> >>>> If so, what is the filesystem ? >>> Ext4 for SO and Ext4 for shared files, but I have created a pool ZFS >>> on this last filesystem (/dev/vdb1). >>> >> If zfs is involved in any way, you will have problems, zfs uses >> nfs4acls, you could try adding 'nfs4acl_xattr' to the 'vfs objects' line. > > this goes in the right direction, but it's zfsacl for ZFS. :) oh, no, hold on, this is about ZFS on Linux I guess? In that case, iirc ZoL uses POSIX ACls and doesn't support NFS4 ACLs, so you shou...

Hi all, I am wondering if there is a way to bypass Samba's ACL checks and delegate access control completely to the underlying file system. My problem arises from the following scenario: Our file system implements ACLs that are to the best of my knowledge currently not readable by any of the existing VFS modules. When trying to access a file with an ACL going beyond the file's POSIX

On Wed, 15 May 2024 13:02:24 +0200 mathias dufresne via samba <samba at lists.samba.org> wrote: > Le mer. 15 mai 2024 ? 12:32, Rowland Penny via samba > <samba at lists.samba.org> a ?crit : > > > On Wed, 15 May 2024 10:36:03 +0200 > > mathias dufresne via samba <samba at lists.samba.org> wrote: > > > > > Hi everyone, > > > > >

...map_ldb:use rfc2307 = yes dns forwarder = 192.168.50.5 nsupdate command = /usr/local/bin/samba-nsupdate -g vfs objects = zfsacl store dos attributes = Yes ea support = yes map acl inherit = Yes ## Usee nfsv4 acls ## => See README.nfs4acls.txt for more information ## Use OWNER@ and GROUP@ special IDs nfs4:mode = special ## Merge duplicate ACEs nfs4:acedup = merge ## Enable changing owner and group nfs4:chown = yes [netlogon] path = /var/db/samba4/sysvol/mbok.co.uk/scripts...

In some spare time, been trying to get Samba 4.10.6-1 working on AIX. Several earlier posts handled by Louis and Rowland. Which were much appreciated and beneficial. Using this stripped (leaving comments out of it) GLOBALS section of smb.conf: [global] workgroup = boost realm = BOOST.COM server string = Samba Server Version %v interfaces = lo eth0

...0PM +0530, Akash Jain wrote: > > > Hi All > > > > > > I found there is one bug in the plugin. The name of the attribute for ACL as > > > per strace output of nfs4_setfacl is system.nfs4_acl. > > > The source code has defined it as > > > #define NFS4ACL_XATTR_NAME      ( "system.nfs4acl" ) > > > > > > Note there is missing underscore. > > > > > > After this, the EOPNOTSUPP error is not observed. > > > > > > Hope this helps > > > > Hmmm. This has been changed for Samba...

...> > > > > > > > > > I found there is one bug in the plugin. The name of the attribute for ACL as > > > > > per strace output of nfs4_setfacl is system.nfs4_acl. > > > > > The source code has defined it as > > > > > #define NFS4ACL_XATTR_NAME      ( "system.nfs4acl" ) > > > > > > > > > > Note there is missing underscore. > > > > > > > > > > After this, the EOPNOTSUPP error is not observed. > > > > > > > > > > Hope this helps...

...9; to [global], but this is jfs2 on AIX. A bit of investigation turned up 'vfs_aixacl2' which I think will do the same thing, try running 'man vfs_aixacl2', if this doesn't work, see here: https://fossies.org/linux/misc/samba-4.11.6.tar.gz/samba-4.11.6/source3/modules/README.nfs4acls.txt If it does work similar to 'vfs_acl_xattr', you should be able to set the permissions from Windows (I am taking it that you do have Windows clients) and remove the 'valid users' etc. Rowland

...)(A;OICI;0x001301bf;;;S-1-5-21-443838659-2890314986-1722269781-1118)(A;OICI;0x001f01ff;;;S-1-5-21-443838659-2890314986-1722269781-500)" sd2 Unknown parameter encountered: "secrets database" 1. Am I doing anything wrong? 2. Is there any correspondence between posix acl's, ntacl, nfs4acl,linux file permissions and what I write in smb.conf? Is there any priority? Thanks. Steve

On Wed, 10 Oct 2018 09:25:16 +0200 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > Hmm.. Bummer.. > I just discovered the debian package dont have the vfs_nfs4acl > include in the build. > > And because of that it's not in my packages. I'll have a look into > it, see what i can make of it. > That is odd, it isn't as if it is a new vfs module, it has been about since 2013. Rowland