> On Thu, Apr 22, 2021 at 09:28:14AM +0900, Namjae Jeon wrote: > > ACLs Partially Supported. only DACLs available, SACLs > > (auditing) is planned for the future. For > > ownership (SIDs) ksmbd generates random subauth > > values(then store it to disk) and use uid/gid > > get from inode as RID for local domain SID. > > The current acl implementation is limited to > > standalone server, not a domain member. > > Integration with Samba tools is being worked on to > > allow future support for running as a domain member. > Hi Bruce, > How exactly is this implementing ACLs? I grepped through the code a bit and couldn't quite figure it > out--it looked like maybe it's both converting to a POSIX ACL and storing the full SBM ACL in an xattr, > is that correct? When you read an ACL, and both are present, which do you use? If 'vfs objects = acl_xattr' parameter is defined in smb.conf, ksmbd store both. If not, only posix acl will be stored. To avoid translation from posix acl to ntacl from request of client, ksmbd use ntacl in xattr first. > > Also it looked like there's some code from fs/nfsd/nfs4acl.c, could we share that somehow instead of > copying? Hm.. I do not know how to share the code with nfsd at present. Maybe we can discuss it again after upstream ? Any thought ? > > --b.
