From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14499] New: expose NT ACLs via system.nfs4_acl EA
Date: Fri, 18 Sep 2020 08:40:37 +0000 [thread overview]
Message-ID: <bug-14499-10630@https.bugzilla.samba.org/> (raw)
https://bugzilla.samba.org/show_bug.cgi?id=14499
Bug ID: 14499
Summary: expose NT ACLs via system.nfs4_acl EA
Product: CifsVFS
Version: 5.x
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: kernel fs
Assignee: sfrench@samba.org
Reporter: bjacke@samba.org
QA Contact: cifs-qa@samba.org
Target Milestone: ---
At SambaXP 2020 the idea came up to expose the NT ACLs via the more commonly
used extended attribute system.nfs4_acl - which is the default attribute also
for NFS4. Those ACLs can be managed with the well known toolset of
nfs4-acl-tools and those ACLs could even be managed by Samba through the
nfs4acl_xattr module. This would improve overall cifs ACL management a lot.
This bug is to folow the status of this idea, is there some rough eta for this,
Steve?
--
You are receiving this mail because:
You are the QA Contact for the bug.
reply other threads:[~2020-09-18 8:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14499-10630@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).