From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Duplicate ACLs? - Can't copy file even with Admin permissions
Date: Wed, 19 Jan 2022 09:00:35 +0100 [thread overview]
Message-ID: <YefFIwM4POThNgRA@calimero.vinschen.de> (raw)
In-Reply-To: <25063.30447.365452.499124@consult.pretender>
On Jan 18 21:26, cygwin@kosowsky.org wrote:
> On Jan 04:14 Corinna Vinschen wrote:
> > I uploaded a developer snapshot to https://cygwin.com/snapshots
> > Please give it a try.
>
> Indeed, the new cygwin.dll does allow me to copy the files and it does
> preserve the 'getfacl' (POSIX) acl's (as above).
> However, it does *not* preserve the full ACL's as reported by 'icacls'.
> [...]
> So, the full Windows ACLs as indicated by 'icacls' differ.
> Is this the expected behavior??? If so, why???
Cygwin converts the DACL into a a POSIX ACL on the API level and Cygwin
tools consequentially read and write POSIX ACLs, which differ from
Windows ACLs.
Corinna
next prev parent reply other threads:[~2022-01-19 8:00 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 [this message]
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=YefFIwM4POThNgRA@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).