public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "" <cygwin@kosowsky.org>
To: cygwin@cygwin.com
Subject: Duplicate ACLs? - Can't copy file even with Admin permissions
Date: Mon, 3 Jan 2022 10:51:07 -0500	[thread overview]
Message-ID: <25043.7019.643488.389876@consult.pretender> (raw)

To: 
Subject:
X-Mailer: VM 8.2.0b under 25.2.2 (x86_64-pc-linux-gnu--text follows this line--
I have a file: /c/Config.Msi/3da9e136.rbf that I cannot copy, even when
I run bash as an administrator -- seemingly due to perm/acl errors.

Specifically:
	# mv 3da9e136.rbf newfile: works
	# cp 3da9e136.rbf newfile: works

But,
	# cp -a 3da9e136.rbf newfile
	cp: preserving permissions for ‘newfile’: Permission denied
	(though the file is created)

If I then do
	# getfacl 3da9e136.rbf | setfacl -f - newfile
	setfacl: more than one user entry.

And:
	# getfacl 3da9e136.rbf
	# file: 3da9e136.rbf
	# owner: Administrators
	# group: SYSTEM
	user::rwx
	group::rwx
	other::r-x
	user::rwx
	group::rwx
	group:SYSTEM:rwx
	mask::rwx
	other::r-x

While:
	# getfacl newfile
	# file: newfile
	# owner: Administrators
	# group: SYSTEM
	user::rwx
	group::rwx
	other::r-x


So the problem seems to be that the 'user' (and presumably also the
'group' and 'other') ACLs are duplicated.

Note that 'subinacl' shows:
=================================
+File C:\Config.Msi\3da9e136.rbf
=================================
/control=0x0
/owner             =builtin\administrators
/primary group     =system
/audit ace count   =0
/perm. ace count   =3
/pace =system  Type=0x0 Flags=0x3 AccessMask=0x1f01ff
/pace =everyone  Type=0x0 Flags=0x3 AccessMask=0x1200a9
/pace =builtin\administrators  Type=0x0 Flags=0x3 AccessMask=0x1f01ff


-----------------------------------------
Not sure if this is an NTFS bug (or feature???) or a problem with
Cygwin file manipulation tools.

Either way:
- Is this a bug? (or a feature????)
- Any idea how or why this happened?
- Any idea how (or whether) to fix this so that I don't have duplicate
  ACLs?

Ideally, I would like to "fix" the problem with Cygwin tools...



             reply	other threads:[~2022-01-03 15:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 15:51 cygwin [this message]
2022-01-05 11:34 ` Corinna Vinschen
2022-01-06 11:12   ` Achim Gratz
2022-01-06 21:11     ` cygwin
2022-01-07 13:22       ` Corinna Vinschen
2022-01-07 20:56       ` cygwin
2022-01-10 10:07         ` Corinna Vinschen
2022-01-10 13:46           ` Corinna Vinschen
2022-01-12  9:33             ` Corinna Vinschen
2022-01-19  2:26             ` cygwin
2022-01-19  8:00               ` Corinna Vinschen
2022-01-21 13:57                 ` cygwin
2022-01-25 19:19                   ` Corinna Vinschen
2022-01-26  1:11                     ` cygwin
2022-01-06 18:05   ` Andrey Repin
2022-01-06 19:42     ` Franz Fehringer
2022-01-06 20:35     ` cygwin
2022-01-06 20:46       ` Eliot Moss

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=25043.7019.643488.389876@consult.pretender \
    --to=cygwin@kosowsky.org \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).