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 18:18:00 -0000 [thread overview]
Message-ID: <ema091e9e3-10a6-4b7d-82af-71a10c2b9077@gaming> (raw)
>Which warning do you mean here?
The "permissions out of order" one. This was not the case before, at
least not on my installation, so I don't see how this can be called
normal.
>Come on, be fair. The new ACL handling started out early 2015, got a
>break when I realized that it doesn't work as is, and then got a new
>test phase starting back in September. Except for minor bugs it seemed
>to work rather well. Nobody reported this effect in all the 4 months
>of
>test period. You don't actually think I wouldn't have fixed it prior
>to the release if I had known about it, do you?
2.4.0-1 was released ~3 weeks ago. I had actually upgraded a few days
earlier to a TEST version and noticed that a cygwin downloaded exe
couldn't be executed but assumed the exe was corrupt and didn't
investigate...
Then a few days ago the same thing happened again. Now I'm here.
Anyway, clearly most users are just that: users, and not testers that
will install and test TEST versions.
>They are not supposed to be modifiable in Explorer. If you want to
>change permissions on a Cygwin ACL, use chmod or setfacl.
Is this a joke?
>
>> Here is the output from icacls /saveacl for some file:
>>
>>D:P(D;;RPWPDTRC;;;S-1-0-0)(A;;0x1f019f;;;S-1-5-21-559282050-488988736-2019639472-1001)(D;;WP;;;AU)(D;;WP;;;SY)(D;;WP;;;BA)(D;;WP;;;BU)(A;;FR;;;S-1-5-21-559282050-488988736-2019639472-513)(A;;0x1201bf;;;AU)(A;;0x1201bf;;;SY)(A;;0x1201bf;;;BA)(A;;0x1200a9;;;BU)(A;;FR;;;WD)
>Doh, I'm sorry, but I can't read this format very well. Can you please
>again send the standard icacls output as well as the output from
>getfacl
>of the parent dir and the created file? I'd like to have this problem
>fixed, but I need your help. As I said, it works fine for me and
>without
>being able to reproduce I'm somewhat at a loss.
You can import this by putting it in a textfile and using icacls
testfile /restore acl.txt.
As I've said before, my Windows is German. icacls output will be
localized. Do you really want that?
What I posted is the only portable way to share ACLs.
>
>> Here is what's "normal" for Windows if I create a file under a new
>>folder on
>> C: in Explorer:
>
>If you don't want POSIX perms, but standard Windows perms, use the
>"noacl"
>mount option. See
>https://cygwin.com/cygwin-ug-net/using.html#mount-table
I guess that is my only option right now.
>
>> Here is what I would expect:
>> MyUser is in the group Administrators. Given the inherited
>>permissions above
>> a Windows-created file should be shown as "-rwxrwxr--+ MyUser
>> Administrators"?
>
>Sorry, can't do that, *unless* you make "Administrators" the primary
>group in your user token(*).
Ok, so the group is "None". No big deal.
So what about fixing the permissions like I described?
So the permissions would be "-rwx------+ MyUser None" in Cygwin for a
Windows-created file with default ACL.
By using the inherited default ACLs there should be at most 3 additional
ACLs (+1 for NULL SID whatever that is doing):
- deny r/w/x for user ("MyUser")
- allow r/w/x for group ("None")
- allow r/w/x for other ("Everyone")
And leaving the inherited ones untouched, right?
But if you scroll up you will see that in my system Cygwin kills the
inheritance and I end up with 12 new ACL entries for each file.
--
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 reply other threads:[~2016-02-10 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 18:18 xnor [this message]
2016-02-10 20:50 ` Andrey Repin
2016-02-10 22:40 ` Re[2]: " xnor
2016-02-10 23:35 ` Andrey Repin
2016-02-11 10:25 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2016-02-10 2:20 Andrey Repin
2016-02-10 17:39 ` Re[2]: " xnor
2016-02-08 18:20 Corinna Vinschen
2016-02-09 20:53 ` Re[2]: " xnor
2016-02-08 14:16 Corinna Vinschen
2016-02-08 17:48 ` 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=ema091e9e3-10a6-4b7d-82af-71a10c2b9077@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).