public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bryan Berns <bryan.berns@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [TESTERS needed] New POSIX permission handling
Date: Sat, 11 Apr 2015 11:11:00 -0000	[thread overview]
Message-ID: <CADi7v6L1QrigKn0-ca-XXD2hSZxT5LTvZL2=xAR5+qrcBCEVZw@mail.gmail.com> (raw)
In-Reply-To: <20150411094414.GC19111@calimero.vinschen.de>

>> >   That means, even if SYSTEM or Administrators have full access to the
>> >   file, the POSIX permssion bits will not reflect that fact.  And while
>> >   other users get access denied based on the mask value, SYSTEM and
>> >   Administrators will never get access denied based on the mask.
>>
>> If you want to put this to better use in larger settings it would seem
>> preferrable if it was possible to define a list of users to treat this
>> way in fstab.
>
> Nope, sorry, no configuration for this.  Either it's handled without
> any exception, or for SYSTEM only, or for SYSTEM+Admins.  But either
> way, we're doing it the same way on every system.

Damn.  I was about to reply with Achim's exact same thought --- like a
file in /etc with a list of SIDs.  I can empathize with Corinna's veto
though -- having a hundred tweak-able settings in Cygwin is
unmaintainable for the general populous.  I may apply a local patch to
extend this ability myself because Cygwin has become rather unusable
for users with home's on our network drives (given all the programs
that attempt to do sanity checks on group perms).

That said, I appreciate what has been integrated --- it will help in
several scenarios.  I will test the release this weekend.  Thanks for
all the hard work!

--
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

  reply	other threads:[~2015-04-11 11:11 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
2015-04-11  9:44   ` Corinna Vinschen
2015-04-11 11:11     ` Bryan Berns [this message]
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='CADi7v6L1QrigKn0-ca-XXD2hSZxT5LTvZL2=xAR5+qrcBCEVZw@mail.gmail.com' \
    --to=bryan.berns@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).