From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Shares with strange ACL settings
Date: Wed, 12 Aug 2015 21:03:00 -0000 [thread overview]
Message-ID: <87vbck8h92.fsf@Rainer.invalid> (raw)
In-Reply-To: <20150812183220.GO13029@calimero.vinschen.de> (Corinna Vinschen's message of "Wed, 12 Aug 2015 20:32:20 +0200")
Corinna Vinschen writes:
>> I think so, but there are likely some corner cases. But I think that
>> had been proposed and shot down already, so I was trying to come up with
>> something less intrusive.
>
> This is relatively unintrusive. The current user token is always
> available. So if owner == current user, for every group in the file's
> ACL just check if it's in the current user token and, if so, add the
> perms of that group to the owner perms.
>
> Sounds pretty neat as an intermediate solution to me.
I'd play the guinea pig for that snapshot… :-)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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 prev parent reply other threads:[~2015-08-12 21:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 8:42 Achim Gratz
2015-08-11 17:20 ` Andrey Repin
2015-08-11 17:29 ` Achim Gratz
2015-08-12 15:26 ` Corinna Vinschen
2015-08-12 15:50 ` Achim Gratz
2015-08-12 15:58 ` Corinna Vinschen
2015-08-12 18:09 ` Achim Gratz
2015-08-12 18:32 ` Corinna Vinschen
2015-08-12 21:03 ` Achim Gratz [this message]
2015-08-13 16:33 ` Corinna Vinschen
2015-08-13 17:48 ` Achim Gratz
2015-08-13 17:53 ` Corinna Vinschen
2015-08-14 8:30 ` Corinna Vinschen
2015-08-14 10:56 ` Achim Gratz
2015-08-14 13:45 ` Corinna Vinschen
2015-08-14 18:25 ` Achim Gratz
2015-08-14 18:43 ` Corinna Vinschen
2015-08-17 8:20 ` Corinna Vinschen
2015-08-15 15:11 ` Achim Gratz
2015-08-15 18:31 ` Corinna Vinschen
2015-08-15 19:04 ` Achim Gratz
2015-08-17 8:28 ` Achim Gratz
2015-08-17 9:03 ` Corinna Vinschen
2015-08-17 9:12 ` Achim Gratz
2015-08-17 10:45 ` Corinna Vinschen
2015-08-17 10:51 ` Achim Gratz
2015-08-17 11:03 ` Corinna Vinschen
2015-08-17 11:09 ` Achim Gratz
2015-08-17 11:31 ` Corinna Vinschen
2015-08-17 11:39 ` Corinna Vinschen
2015-08-17 11:43 ` Achim Gratz
2015-08-17 12:42 ` Achim Gratz
2015-08-17 12:56 ` Corinna Vinschen
2015-08-17 13:12 ` Achim Gratz
2015-08-17 14:53 ` Corinna Vinschen
2015-08-17 15:47 ` Achim Gratz
2015-08-17 16:11 ` Corinna Vinschen
2015-08-15 15:41 ` Marco Atzeri
2015-08-15 18:32 ` Corinna Vinschen
2015-08-13 17:56 ` 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=87vbck8h92.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).