From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: win dirs don't handle lack of inherited rule(?): getfacl + tar dir Warning: Cannot acl_to_text: Invalid argument
Date: Fri, 15 Mar 2019 12:25:00 -0000 [thread overview]
Message-ID: <bb9bf5e7-5804-7dac-80d3-a58db02b4a26@SystematicSw.ab.ca> (raw)
In-Reply-To: <20190313113445.GX3785@calimero.vinschen.de>
On 2019-03-13 05:34, Corinna Vinschen wrote:
> Per POSIX, the normal acl (ACL_TYPE_ACCESS) and the inheritance acl
> (ACL_TYPE_DEFAULT) are two separate lists. So we have the
> ACL_TYPE_ACCESS with 9 entries and the ACL_TYPE_DEFAULT with 0 entries.
>
> And while empty ACL_TYPE_DEFAULT acls are valid per POSIX, the Cygwin
> function creating the text representation for an acl didn't allow
> empty acls.
>
> I pushed a patch and uploaded new developer snapshots to
> https://cygwin.com/snapshots/
In my experience no DACLs results in no POSIX permissions for Cygwin programs,
although Explorer and some other Windows programs can see and read them.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-03-15 12:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 3:36 L A Walsh
2019-03-08 12:15 ` Corinna Vinschen
2019-03-10 10:48 ` L A Walsh
2019-03-10 11:20 ` Corinna Vinschen
2019-03-10 13:35 ` Andrey Repin
2019-03-10 16:38 ` L A Walsh
2019-03-10 22:50 ` Andrey Repin
2019-03-10 23:15 ` L A Walsh
2019-03-10 14:09 ` Brian Inglis
2019-03-12 15:45 ` L A Walsh
2019-03-12 16:36 ` Corinna Vinschen
2019-03-13 2:22 ` L A Walsh
2019-03-13 9:19 ` Corinna Vinschen
2019-03-13 9:32 ` Corinna Vinschen
2019-03-13 11:34 ` Corinna Vinschen
2019-03-15 2:46 ` L A Walsh
2019-03-15 9:17 ` Corinna Vinschen
2019-03-15 12:25 ` Brian Inglis [this message]
2019-03-15 13:34 ` Corinna Vinschen
2019-03-15 14:46 ` L A Walsh
2019-03-15 14:52 ` Corinna Vinschen
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=bb9bf5e7-5804-7dac-80d3-a58db02b4a26@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).