similar to: Multiprotocol File Sharing via NFSv4 and Samba

FreeNAS / FreeBSD have native NFSv4 ACLs. They do however lack kernel oplock support so there are perhaps some caveats in that regard. On Thu, Jul 2, 2020 at 3:07 PM Strahil Nikolov via samba < samba at lists.samba.org> wrote: > Hi Kraus, > > I know that Gluster can be exported over NFS-Ganesha (supports v4.X), > Samba (protocol 1.0 in order to get 'real'

Hi Kraus, I know that Gluster can be exported over NFS-Ganesha (supports v4.X), Samba (protocol 1.0 in order to get 'real' permissions), Apple's stuff and if you rebuild the source - you can use the built-in gNFS (supports NFS v3 over tcp) all at once. Yet, I'm not sure about the ACLs, so you should either test it yourself or ask on the gluster mailing list. Deployment

Dear all, what is about the support for POSIX ACL in Samba protocol implementation of SMB2 and SMB3? >From what I extracted from SNIA and SambaXP developer conference talks and as well as the official Samba Wiki, support for POSIX ACL in SMB2 and SMB3 has been completely abandonned. Am I right? If so, is there any other possibility to allow Linux Clients to natively access access control lists

Hi Jeremy, Hi Steve, Hi Ronnie, thanks for your replies and the profound discussion. I think, it's best to demonstrate my problem case along an real world example: The following log of a console sesssion shows how I am doing the mounts on behalf Linux Kernel CIFS-FS Module on the client side against a Samba 4.5 file server (both running on Debian Stretch 9.8) via SMB/CIFS resp. SMB2 protocol:

Dear samba folks, I have a special question regarding the simultaneous operation of nscd and winbindd on the same host: We are running in a Samba file server setup where the nsswitch.conf looks like this: passwd: files ldap group: files ldap shadow: files ldap hosts: files dns wins networks: files protocols: db files services: db files

Hi all, I am testing different setups for Samba home share mounts via the CIFS protocol on Linux clients with and without Keberos security (both krb5 and krb5i). I am experiencing some strange behaviour in case of Kerberos authentication: In case of mounts (by root or the user itself) without Kerberos security (only NTLMv2 authentication), local root and the owning user on the Linux client

On Tue, Feb 26, 2019 at 09:03:41AM -0800, Jeremy Allison via samba wrote: > > Check out the latest cifsfs code. I think Steve > and Aurelian and Ronnie added an ioctl for this. > > I'm here at Vault in Boston with Steve, I'll ask > him :-). Steve says there are two utilities in Linux, getcifsacl and setcifsacl that use a custom ioctl inside the Linux cifsfs kernel

Thanks for the first reply, Jeremy. What about the (future) implementation of RichACL? Will there be any native Linux Client support along with the SMB2/SMB3 protocol? I know, there is a native implemenation for RichACLs in ext4 FS. Unfortunately, smbcals is not a native Linux ACL Tool and has a very unhandy syntax. I just tested some days ago. ;-) I am looking for a solution that allows the

I passed by the changelog for the Linux CIFS Kernel Module at https://wiki.samba.org/index.php/LinuxCIFSKernel. The following two sections caught my attention: >> 4.19 Kernel (69 changesets, module version 2.13) >>Allow cifs.ko to be built with insecure dialects disabled (vers=1.0 and vers=2.0 not allowed). Add support for snapshot >> mounts (specifying "snapshot="

Hi. I have created some zfs-partitions. First I create the home/user-partitions. Beneath that I create additional partitions. Then I have do a chown -R for that user. These partitions are shared using the sharenfs=on. The owner- and group-id is 1009. These partitions are visible as the user assigned above. But when I mount the home/user partition from a FreeBSD-client, only the top-partiton has

Dear Jeremy, thanks for your instant reply. :-) Along with Linux native getfacl/fetfacl, I also tested getcifsacl/setcifsacl (for sure thoroughly ;-)). Unfortunately, these CIFS client tools seem to have been designed as part of the "old" CIFS Unix Extensions, working only for SMB/CIFS mounts, and are not supposed to work with SMB2/SMB3 mounts, as I guess. During my tests, the

>From what I've read so far Samba supports POSIX ACLs, correct? If so, will they work over NFSv4 exports? The reason I'm asking is as follows: We're considering redoing our storage systems which currently also house Samba servers. These are currently running on Linux boxes with NFS exports to the rest of our networks. Many machines with massive amounts of storage, one Samba

hi there - is it possible to share a directory via samba and (kernel-)nfsv4 in parallel and make samba use (ie.: read, write and enforce) nfsv4 acls to implement winnt-acls? i know that using nfs3 and posix acls is working halfway okay, but couldn't find anything useful for nfsv4 and the associated acls - sorry if i missed something obvious. i played around with the nfs4acl_xattr and

Could you see if anything useful in the logs indicating why the ACL was not returned? Instructions are at: https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Enabling_Debugging (it is easier for newer kernels due to dynamic tracing e.g. "trace-cmd record -e cifs" but even with these older kernels it should be enough information in the dmesg logs - if not a wireshark trace

I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead of "Access Denied" errors that I currently get. Looking at the Samba source, the only obvious NFSv4 stuff appears to be the following: - zfsacl, available

hi all, i'm managing a large installation of a dovecot cluster in director + NFS backend architecture and we are moving from NFSv3 to NFSv4. Our NFS server is a Netapp in clustered mode and reading technical specs of NFSv4 delegation feature it seems that enabling delegation in this type of dovecot architecture should bring great benefits: only one backend server access a specific mailbox at a

> On Dec 3, 2015, at 17:24, Jeremy Allison <jra at samba.org> wrote: > >> On Thu, Dec 03, 2015 at 03:54:21PM -0700, Nick Couchman wrote: >> I have a situation where I need to share, via Samba, a filesystem mounted via NFSv4. I'm struggling with the best way to make Samba see the NFSv4 ACLs and enumerate them to provide the proper SMB/CIFS access to the files, instead

Hi Timo, I just read about NFSv4 now being included in SuSE and Redhat Enterprise versions, and although I don't use it myself, wondered how this will impact Dovecot for those using it? Will it make life easier? Or is it even supported currently? Just curious... thanks... -- Best regards, Charles

Alessio Cecchi wrote: [...] > Have you already try to run NFSv4? it's in place on a (very) small sample of mailboxes in dbox format, no issues up to now (Debian Wheezy mainline kernel) > When we switch to netapp and nfsv4 we had many problems (lock problems > and instability) and we had to go immediately to NFSv3. I don't know if > was a netapp problem or nfs client (Debian

Good morning, folks. I'm involved in a project to enforce NFSv4 ACL's across a variety of storage platforms, in particular NetApps sharing NFS. That works fiine with the NetApp NFS qtrees, but we'd like to share those with CIFS clients as well. This works, and restricts access the way we expect NFSv4 ACL's to work, but the Windows clients cannot view any of the security settings