From: Russ Allbery <rra@stanford.edu>
To: Garance A Drosihn <drosih@rpi.edu>
Cc: Linus Torvalds <torvalds@transmeta.com>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org, <linux-fsdevel@vger.kernel.org>,
<openafs-devel@openafs.org>
Subject: Re: [OpenAFS-devel] Re: Alternative to PAGs
Date: Thu, 15 May 2003 17:46:48 -0700 [thread overview]
Message-ID: <yl7k8rzpjb.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <p05210620bae9cce008ed@[128.113.24.47]> (Garance A Drosihn's message of "Thu, 15 May 2003 19:14:27 -0400")
Garance A Drosihn <drosih@rpi.edu> writes:
> What AFS does not want is for a single process to be drosehn@rpi.edu and
> linus@rpi.edu at the exact same time. That is to avoid the question of
> what open() should do on a file which is permitted:
> drosehn rlidwka
> linus none
An even better example without an obvious answer (which in this case is
that the open should be allowed, since that ACL says that drosehn should
be able to open the file and says nothing about linus) would be if linus
had negative rights (in other words, if the ACL actively asserted that
linus should *not* be able to open the file regardless of the other ACLs).
AFS supports the notion of negative rights primarily in combination with
groups, so you can have a situation like:
Normal rights:
organization:itss rlidwka
Negative rights:
rra rlidwka
where rra is a member of organization:itss. rra will be denied access to
that directory despite the fact that his membership in organization:itss
would normally give him full rights.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2003-05-16 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 14:15 David Howells
2003-05-15 16:53 ` Linus Torvalds
2003-05-15 23:14 ` [OpenAFS-devel] " Garance A Drosihn
2003-05-16 0:46 ` Russ Allbery [this message]
2003-05-16 0:43 ` Garance A Drosihn
2003-05-16 0:56 ` Nathan Neulinger
2003-05-16 11:08 ` David Howells
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=yl7k8rzpjb.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
--cc=dhowells@redhat.com \
--cc=drosih@rpi.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-devel@openafs.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®