From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14493] New: Conventional tools for managing ACLs can mislead the user
Date: Tue, 15 Sep 2020 02:10:18 +0000 [thread overview]
Message-ID: <bug-14493-10630@https.bugzilla.samba.org/> (raw)
https://bugzilla.samba.org/show_bug.cgi?id=14493
Bug ID: 14493
Summary: Conventional tools for managing ACLs can mislead the
user
Product: CifsVFS
Version: 3.x
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: kernel fs
Assignee: sfrench@samba.org
Reporter: micah.veilleux@iba-group.com
QA Contact: cifs-qa@samba.org
Target Milestone: ---
On a client to a Samba share for which Windows ACLs are configured, "ls -l"
reports incorrect information, and no "+" is present to indicate that ACLs have
been configured:
------------------------------
mcrs3:/TCS # ls -lh testfile
-rwxr-xr-x 1 root root 0 Sep 14 23:05 testfile # permissions are incorrect,
"+" is missing, and owner and primary group owner are incorrect
mcrs3:/TCS # smbcacls //mcrs3/TCS /testfile -k yes
REVISION:1
CONTROL:SR|DP
OWNER:VPTC3\cifsuser
GROUP:VPTC3\Domain Users
ACL:VPTC3\Domain Admins:ALLOWED/0x0/RWDPO
ACL:VPTC3\cifsuser:ALLOWED/0x0/RWDPO
mcrs3:/TCS #
------------------------------
Still on the client, "chown" and "chmod" fail without error:
------------------------------
mcrs3:/TCS # chown vptc3\\mveil testfile
mcrs3:/TCS # chmod u+x testfile
mcrs3:/TCS #
mcrs3:/TCS # smbcacls //mcrs3/TCS /testfile -k yes
REVISION:1
CONTROL:SR|DP
OWNER:VPTC3\cifsuser
GROUP:VPTC3\Domain Users
ACL:VPTC3\Domain Admins:ALLOWED/0x0/RWDPO
ACL:VPTC3\cifsuser:ALLOWED/0x0/RWDPO
mcrs3:/TCS #
------------------------------
On the server side, these issues are not present:
------------------------------
mcrs3:/.TCS_local # ls -l testfile
-rw-rwx---+ 1 VPTC3\cifsuser VPTC3\domain users 0 Sep 14 23:05 testfile
mcrs3:/.TCS_local #
mcrs3:/.TCS_local # smbcacls //mcrs3/TCS /testfile -k yes
REVISION:1
CONTROL:SR|DP
OWNER:VPTC3\cifsuser
GROUP:VPTC3\Domain Users
ACL:VPTC3\Domain Admins:ALLOWED/0x0/RWDPO
ACL:VPTC3\cifsuser:ALLOWED/0x0/RWDPO
mcrs3:/.TCS_local #
mcrs3:/.TCS_local # chown vptc3\\mveil testfile
mcrs3:/.TCS_local # chmod u+x testfile
mcrs3:/.TCS_local #
mcrs3:/.TCS_local # smbcacls //mcrs3/TCS /testfile -k yes
REVISION:1
CONTROL:SR|DP
OWNER:VPTC3\mveil
GROUP:VPTC3\Domain Users
ACL:VPTC3\mveil:ALLOWED/0x0/FULL
ACL:VPTC3\Domain Users:ALLOWED/0x0/
ACL:VPTC3\Domain Users:ALLOWED/0x0/
ACL:VPTC3\Domain Admins:ALLOWED/0x0/RWDPO
ACL:VPTC3\cifsuser:ALLOWED/0x0/RWDPO
ACL:Everyone:ALLOWED/0x0/
mcrs3:/.TCS_local #
mcrs3:/.TCS_local # ls -l testfile
-rwxrwx---+ 1 VPTC3\mveil VPTC3\domain users 0 Sep 14 23:05 testfile
mcrs3:/.TCS_local #
------------------------------
My sernet-samba version is 99:4.12.2-11.suse150.
My mount is:
------------------------------
mcrs3:/TCS # grep "TCS " /etc/fstab
//mcrs3/TCS /TCS cifs
user=cifsuser,multiuser,domain=VPTC3,sec=krb5,mfsymlinks,vers=3.0 0 0
mcrs3:/TCS #
------------------------------
--
You are receiving this mail because:
You are the QA Contact for the bug.
next reply other threads:[~2020-09-15 2:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 2:10 samba-bugs [this message]
2020-09-15 6:48 ` [Bug 14493] Conventional tools for managing ACLs can mislead the user samba-bugs
2020-09-15 16:41 ` samba-bugs
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-14493-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).