From: "" <cygwin@kosowsky.org>
To: cygwin@cygwin.com
Subject: Re: Duplicate ACLs? - Can't copy file even with Admin permissions
Date: Fri, 21 Jan 2022 08:57:35 -0500 [thread overview]
Message-ID: <25066.48079.253017.253466@consult.pretender> (raw)
In-Reply-To: <YefFIwM4POThNgRA@calimero.vinschen.de>
Hi Corinna,
I found another file with ACLs that fail even under the new snapshot
cygwin1.dll.
#getfacl setup.ilg
# file: setup.ilg
# owner: Administrators
# group: None
getfacl: setup.ilg: Invalid argument
#icacls.exe setup.ilg
setup.ilg NT SERVICE\TrustedInstaller:(I)(F)
NT SERVICE\TrustedInstaller:(I)(CI)(IO)(F)
NT AUTHORITY\SYSTEM:(I)(F)
NT AUTHORITY\SYSTEM:(I)(OI)(CI)(IO)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Administrators:(I)(OI)(CI)(IO)(F)
BUILTIN\Users:(I)(RX)
BUILTIN\Users:(I)(OI)(CI)(IO)(GR,GE)
CREATOR OWNER:(I)(OI)(CI)(IO)(F)
#icacls.exe setup.ilg /save setup.acl
#cat setup.acl
setup.ilg
D:(A;ID;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;CIIOID;GA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)(A;ID;FA;;;SY)(A;OICIIOID;GA;;;SY)(A;ID;FA;;;BA)(A;OICIIOID;GA;;;BA)(A;ID;0x1200a9;;;BU)(A;OICIIOID;GXGR;;;BU)(A;OICIIOID;GA;;;CO)
-------------
Any thoughts on what might be wrong here?
next prev parent reply other threads:[~2022-01-21 13:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 15:51 cygwin
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 [this message]
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=25066.48079.253017.253466@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).