From: xnor <xnoreq@gmail.com>
To: cygwin@cygwin.com
Subject: Re[2]: Issues with ACL settings after updating to the latest cygwin.dll
Date: Wed, 10 Feb 2016 17:39:00 -0000 [thread overview]
Message-ID: <emdc328b81-98cd-4ffa-b33c-c768c6a218cc@gaming> (raw)
In-Reply-To: <486885659.20160210050721@yandex.ru>
>It was always the case.
>Permissions are NOT REQUIRED to be ordered in a specific way, but
>Explorer is
>only capable of editing them in the only one way.
>Means, Explorer is deficient. Explorer. Not Windows. Windows is
>perfectly
>capable of handling the Cygwin ACL in the intended way.
No, it really wasn't.
The ACLs were fine until the change in the new Cygwin version. Now there
are 12 ACL entries, all non inherited / inheritance is broken, for each
file...
Also, I always ways able to change ACLs through Explorer without
warnings, which I need to do from time to time.
I'm sorry but all of this can be summed up as bad design.
I've explained what ACLs should be added by Cygwin in a related message.
By making use of default, inherited ACLs, at most 3 (+1 for whatever
NULL SID is doing ...) are needed. At least I see no reason why there
should be such a bloat.
Besides, if cygwin set ACLs properly on the root folder this could be
reduced to 0 additional non-inherited ACLs for many files.
--
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:[~2016-02-10 17:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 20:46 K Stahl
2016-02-08 14:16 ` Corinna Vinschen
2016-02-08 17:48 ` Re[2]: " xnor
2016-02-08 18:12 ` Re[3]: " xnor
2016-02-08 18:22 ` Corinna Vinschen
2016-02-08 18:20 ` Corinna Vinschen
2016-02-09 20:53 ` Re[2]: " xnor
2016-02-10 2:20 ` Andrey Repin
2016-02-10 17:39 ` xnor [this message]
2016-02-10 18:35 ` Andrey Repin
2016-02-10 11:55 ` Corinna Vinschen
2016-02-10 12:19 ` Corinna Vinschen
2016-02-08 18:33 ` Re[3]: " xnor
2016-02-09 15:02 ` K Stahl
2016-02-10 11:56 ` Corinna Vinschen
2016-02-10 18:18 Re[2]: " xnor
2016-02-10 20:50 Andrey Repin
2016-02-10 22:40 ` Re[2]: " xnor
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=emdc328b81-98cd-4ffa-b33c-c768c6a218cc@gaming \
--to=xnoreq@gmail.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).