From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.0.0-0.7
Date: Sat, 18 Apr 2015 11:07:00 -0000 [thread overview]
Message-ID: <20150418110755.GM3657@calimero.vinschen.de> (raw)
In-Reply-To: <87d2314srf.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]
On Apr 18 12:48, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Right. It's a compromise. I take it you don't like the extra behaviour
> > for SYSTEM/Admins. Neither do I. Others are desperately waiting for
> > more. The problem with compromises is, they are usually best if nobody
> > is completely satisfied ;)
>
> I have argued against treating them differently, purely based on
> consistency between the Windows and POSIX world (where possible at all).
> Other considerations have prevailed (maybe rightly so), so I'm not too
> surprised to find some inconsistency in the results.
Neither am I. We're walking a fine line between two very different
systems handling ACLs.
> I don't think you'll find a UN*X system that reports executable
> permission on a plain file simply because root accesses it (for a
> directory it would do that of course). The situation in the above case
> is on the face of it different (the ACL actually has the executable bit
> set), but as I understand you've been wanting to treat both secondaries
> like the root account. I think it would be more sensible to ignore that
> execute permission on plain files when otherwise none is granted (since
> chmod will never mask it). That would eliminate another reason to
> entirely remove the default/inherited ACL and I don't think it has any
> consequences on the Windows side.
Hang on. As far as access(2) is concerned, Cygwin can't ignore the
execute permssions since the OS has its say here. I don't think it's
overly helpful to tweak the result after the OS returned it, dependent
on the user being SYSTEM or having the Admins group in the token.
That's a lot of extra work for a questionable gain.
What we *could* try to do is to tweak the actual SYSTEM and Admins ACE,
though. Rather than ignoring the CLASS_OBJ/ACL_MASK value completely
for them, we could apply the execute bit part only. Usually it doesn't
make sense for SYSTEM/Admins having execute perms if nobody else has
since it's with high probability no executable file.
Would that make sense?
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-18 11:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 11:03 Corinna Vinschen
2015-04-17 20:10 ` Achim Gratz
2015-04-18 8:39 ` Corinna Vinschen
2015-04-18 9:47 ` Achim Gratz
2015-04-18 10:20 ` Corinna Vinschen
2015-04-18 10:48 ` Achim Gratz
2015-04-18 11:07 ` Corinna Vinschen [this message]
2015-04-19 6:05 ` Achim Gratz
2015-04-21 9:33 ` Achim Gratz
2015-04-21 12:16 ` Corinna Vinschen
2015-04-21 17:19 ` Achim Gratz
2015-04-22 9:04 ` Corinna Vinschen
2015-04-22 18:35 ` Achim Gratz
2015-04-23 8:34 ` Corinna Vinschen
2015-04-23 18:45 ` Achim Gratz
2015-04-23 19:49 ` Corinna Vinschen
2015-04-24 2:14 ` random user
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=20150418110755.GM3657@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).