From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.4
Date: Mon, 21 Dec 2015 15:01:00 -0000 [thread overview]
Message-ID: <20151221150119.GG4034@calimero.vinschen.de> (raw)
In-Reply-To: <5677FD30.20502@towo.net>
[-- Attachment #1: Type: text/plain, Size: 2828 bytes --]
On Dec 21 14:22, Thomas Wolff wrote:
> On 23.10.2015 14:25, Corinna Vinschen wrote:
> >On Oct 23 14:22, Corinna Vinschen wrote:
> >>On Oct 23 11:06, Achim Gratz wrote:
> >>>I don't have much time to test it right now (and won't have any time at all
> >>>next week), but so far things look good. The problem with the 0.2 test
> >>>version with UID/GID mapping and not recognizing the primary domain in some
> >>>cases is gone (might have been a fluke anyway). Correlating the output from
> >>>getfacl and icacls still requires some mental gymnastics, but I didn't find
> >>>any obvious errors in the mode bits and ACL so far, which means that things
> >>>like rsync (and some file tests) will now return the correct results for the
> >>>cases I've looked at.
> >>You won't believe how grateful I am having you testing this. Thank you!
> >>
> >>Would you mind to read the comment at the start of sec_acl.cc?
> >https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/sec_acl.cc;hb=a8ec1e804ee9ba2d6f8304731e593dcf167c9836#l27
> >
> >>I'd be
> >>very interested in learning if the description is meaningful enough to
> >>other developers. I also fear we need to have an improved documentation
> >>explaining how this works and what NOT to do, e.g., reorder ACLs :|
> Sorry for the late response...
> The description is mostly meaningful. Just the coexistence of X and X_OBJ
> entries isn't self-explanatory.
I think I don't quite understand what you mean. As the developer I'm
working under the assumption that the posix ACL description is known
(not wanting to explain this from scratch in the sources).
- USER_OBJ refers to the owner of the file. Only one such entry
exists and is equivalent to the POSIX permission bits for the owner.
- GROUP_OBJ refers to the owning group of the file. Only one such
entry exsist, same as for USER_OBJ.
- USER is an entry for a secondary user. There can be an arbitrary
number up to a system-defined maximum of them. E.g, Peter is owner of
the file, so he's the one refered to by the USER_OBJ entry. Paul has
an additonal entry in the ACL with, say, rw- perms. Paul's permissions
are given by a USER entry "user:paul:rw-".
- GROUP is an entry for a secondary group. Any number up to a system-defined
maximum entries are possible. E.g, the owner is Paul (USER_OBJ), the
group is Users (GROUP_OBJ), there's an additional entry for the
Administrators group giving them Full Access. This one is a GROUP
entry "group:Administrators:rwx".
Does this make it clearer? Is there still something missing in the
source comment?
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-21 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 1:52 Corinna Vinschen
2015-10-23 12:35 ` Achim Gratz
2015-10-23 12:55 ` Corinna Vinschen
2015-10-23 13:10 ` Corinna Vinschen
2015-12-21 13:23 ` Thomas Wolff
2015-12-21 15:01 ` Corinna Vinschen [this message]
2015-10-23 14:52 ` Achim Gratz
2015-10-26 11:13 ` Corinna Vinschen
2015-10-26 16:14 ` Achim Gratz
2015-10-27 10:10 ` Corinna Vinschen
2015-10-27 13:28 ` Achim Gratz
2015-10-27 15:11 ` Corinna Vinschen
2015-12-06 9:58 ` Achim Gratz
2015-12-06 14:08 ` Corinna Vinschen
2015-12-06 14:29 ` Achim Gratz
2015-12-06 19:04 ` Corinna Vinschen
2015-12-06 19:50 ` Achim Gratz
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=20151221150119.GG4034@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).