From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [TESTERS needed] New POSIX permission handling
Date: Sat, 11 Apr 2015 14:31:00 -0000 [thread overview]
Message-ID: <20150411143125.GI7343@calimero.vinschen.de> (raw)
In-Reply-To: <5529151E.8000704@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
On Apr 11 14:35, David Macek wrote:
> On 11. 4. 2015 11:59, Corinna Vinschen wrote:
> >> Out of curiosity, does the code somehow distinguish ACLs that don't
> >> have these default permissions (or have different permissions set for
> >> SYSTEM / Administrators)?
> >
> > I don't quite understand the question.
> >
> > For a start, I'd like to point out how POSIX ACLs are supposed to work.
> > http://linux.die.net/man/5/acl is a good start. This is our role model.
>
> I'm gonna read that.
>
> > The new code will compute the mask the same way as before, but it
> > skips the permissions of SYSTEM and Administrators while doing that.
> > That means, the POSIX group permission bits are not affected by
> > the Windows-typical permissions of SYSTEM and Administrators.
> >
> > Example:
> >
> > User rw-
> > Primary group r--
> > Other user rw-
> > Other group r--
> > SYSTEM rwx
> > Everyone ---
> >
> > The computed POSIX MASK/CLASS_OBJ value in Cygwin 1.7.35 is the sum
> > of all group and secondary user permissions
> >
> > rw- | r-- | rwx == rwx
> >
> > The new code ignores SYSTEM, thus the mask is
> >
> > rw- | r-- == rw-
> >
> > Does this explain it sufficiently?
>
> Yes, thank you. My question was about the case where SYSTEM or
> Administrator doesn't have the typical permissions. From this
> explanation, I assume that I won't be able to see any difference in
> the mask in that case, but it doesn't seem to be a bad thing.
I'm seriously hoping so.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-11 14:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 10:07 Corinna Vinschen
2015-04-10 21:13 ` Warren Young
2015-04-11 9:35 ` Corinna Vinschen
2015-04-11 0:00 ` Steven Penny
2015-04-11 9:40 ` Corinna Vinschen
2015-04-11 10:07 ` Corinna Vinschen
2015-04-11 16:26 ` Ernie Rael
2015-04-12 8:22 ` Corinna Vinschen
2015-04-11 10:23 ` Corinna Vinschen
2015-04-11 10:47 ` Steven Penny
2015-04-11 14:30 ` Corinna Vinschen
2015-04-11 16:05 ` Andrey Repin
2015-04-12 17:37 ` Adam Dinwoodie
2015-05-16 2:39 ` Steven Penny
2015-05-17 7:44 ` Duncan Roe
2015-05-19 7:52 ` Jiří Engelthaler
2015-04-11 8:47 ` Achim Gratz
2015-04-11 9:02 ` David Macek
2015-04-11 9:08 ` Achim Gratz
2015-04-11 9:51 ` David Macek
2015-04-11 11:51 ` Achim Gratz
2015-04-11 10:00 ` Corinna Vinschen
2015-04-11 12:36 ` David Macek
2015-04-11 14:31 ` Corinna Vinschen [this message]
2015-04-11 9:44 ` Corinna Vinschen
2015-04-11 11:11 ` Bryan Berns
2015-04-11 14:32 ` Corinna Vinschen
2015-04-11 16:05 ` Andrey Repin
2015-04-11 17:11 ` donmez
2015-04-12 8:35 ` Corinna Vinschen
2015-04-12 13:21 ` İsmail Dönmez
2015-04-12 14:25 ` Corinna Vinschen
2015-04-15 15:42 ` Corinna Vinschen
2015-04-16 10:20 ` Ismail Donmez
2015-04-16 11:03 ` Corinna Vinschen
2015-04-16 16:09 ` Ismail Donmez
2015-04-16 16:24 ` Corinna Vinschen
2015-04-16 16:48 ` Ismail Donmez
2015-04-17 7:30 ` Corinna Vinschen
2015-04-17 10:06 ` Corinna Vinschen
2015-04-17 15:17 ` Ismail Donmez
2015-04-17 16:22 ` 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=20150411143125.GI7343@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).