From: "Benjamin Huntsman" <BHuntsman@mail2.cu-portland.edu>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] permissions
Date: Sat, 16 Oct 2010 23:36:24 -0700 [thread overview]
Message-ID: <621112A569DAE948AD25CCDCF1C075332999FA@dolly.ntdom.cupdx> (raw)
In-Reply-To: <a76d4d2bb0de9e139a3ec17ee47a3c60@plug.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
>to elaborate: group permission is not implemented by any
>kernel file servers in the standard distribution.
And yet, it honors "others" permissions? I can set the r
bit on others, and the cat then works...
-----Original Message-----
From: 9fans-bounces@9fans.net on behalf of erik quanstrom
Sent: Sat 10/16/2010 11:19 PM
To: 9fans@9fans.net
Subject: Re: [9fans] permissions
On Sun Oct 17 02:02:07 EDT 2010, skip.tavakkolian@gmail.com wrote:
> group membership checking is up to the particular file server. if it
> doesn't implement it, it wont be enforced.
to elaborate: group permission is not implemented by any
kernel file servers in the standard distribution. only a few
non-kernel filesystems bother with group ownership. all
of them are fileservers that store files on disk (e.g. fossil,
kenfs).
in theory, one could, involve the auth server in the process,
so that a user could use the auth serve to prove he's part of
a group, but nobody's done anything like that yet.
- erik
[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2954 bytes --]
next prev parent reply other threads:[~2010-10-17 6:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 5:35 Benjamin Huntsman
2010-10-17 6:00 ` Skip Tavakkolian
2010-10-17 6:19 ` erik quanstrom
2010-10-17 6:36 ` Benjamin Huntsman [this message]
2010-10-17 13:59 ` erik quanstrom
2010-10-17 16:01 ` blstuart
2010-10-17 16:11 ` erik quanstrom
2010-10-17 17:17 ` ron minnich
2010-10-17 18:11 ` Benjamin Huntsman
2010-10-17 18:18 ` erik quanstrom
2010-10-17 19:17 ` blstuart
2010-10-17 19:59 ` Benjamin Huntsman
2010-10-17 20:40 ` blstuart
2010-10-17 21:22 ` Benjamin Huntsman
2010-10-17 22:56 ` erik quanstrom
2010-10-18 9:00 ` Steve Simon
2010-10-18 9:29 ` dave.l
2010-10-18 9:34 ` Bruce Ellis
2010-10-18 11:07 ` Dave Eckhardt
2010-10-18 11:11 ` Bruce Ellis
2010-10-17 22:58 ` blstuart
2010-10-19 18:18 ` Nathaniel W Filardo
2010-10-17 23:00 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
2001-10-18 14:28 Russ Cox
2001-10-23 20:34 ` Matthew Hannigan
2001-10-24 8:44 ` Douglas A. Gwyn
2001-10-18 14:00 Russ Cox
2001-10-18 14:12 ` Lucio De Re
2001-10-18 13:56 Lucio De Re
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=621112A569DAE948AD25CCDCF1C075332999FA@dolly.ntdom.cupdx \
--to=bhuntsman@mail2.cu-portland.edu \
--cc=9fans@9fans.net \
/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).