From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "Kirk McKusick" <mckusick@mckusick.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Additional groups and additional directory permissions
Date: Sat, 10 Aug 2019 08:02:03 +0200 [thread overview]
Message-ID: <51fd4ffbdeb80edffe8f837f04edf1aa@firemail.de> (raw)
In-Reply-To: <201908100402.x7A42p7C008714@chez.mckusick.com>
thanks a lot!
--- Ursprüngliche Nachricht ---
Von: Kirk McKusick <mckusick@mckusick.com>
Datum: 10.08.2019 06:02:51
An: Clem Cole <clemc@ccc.com>
Betreff: Re: [TUHS] Additional groups and additional directory permissions
>
> Late to answer...
>
> As far as I remember, Clem's description is correct. The filesystem
> itself stores only one owner and one group ID. When checking access
> to the file, the file owner is checked to see if the user ID matches.
> If so, then the owner permissions are applied. If not then the group
> array associated with the user is used to decide if the group of the
> file matches one of the groups of which the user is a member and if
> so the group permissions apply. Otherwise the other permissions are
> used.
>
> In BSD, the group assigned to the file is assigned from the group of
> the directory in which it is created. The setgid flag can be set only
> if that group is a member of the user's group array. The user can only
> change the group ID to one that appears in their group array.
>
> Until multiple group sets were added to System V, the group of the
> file was taken from the gid assigned to the user at login.
>
> Kirk McKusick
>
next prev parent reply other threads:[~2019-08-10 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 4:02 Kirk McKusick
2019-08-10 6:02 ` Thomas Paulsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-02 19:44 Norman Wilson
2019-08-01 12:35 [TUHS] Who's behind the UNIX filesystem permission Doug McIlroy
2019-08-01 16:22 ` John P. Linderman
2019-08-02 8:35 ` [TUHS] Additional groups and additional directory permissions arnold
2019-08-02 11:18 ` Tony Finch
2019-08-04 6:40 ` arnold
2019-08-02 12:45 ` Arthur Krewat
2019-08-02 13:06 ` Clem Cole
2019-08-02 13:28 ` Clem Cole
2019-08-02 19:00 ` Thomas Paulsen
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=51fd4ffbdeb80edffe8f837f04edf1aa@firemail.de \
--to=thomas.paulsen@firemail.de \
--cc=mckusick@mckusick.com \
--cc=tuhs@tuhs.org \
/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 NNTP newsgroup(s).