mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Garance A Drosihn <drosih@rpi.edu>
To: Linus Torvalds <torvalds@transmeta.com>,
	David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, <linux-fsdevel@vger.kernel.org>,
	<openafs-devel@openafs.org>
Subject: [OpenAFS-devel] Re: Alternative to PAGs
Date: Thu, 15 May 2003 19:14:27 -0400	[thread overview]
Message-ID: <p05210620bae9cce008ed@[128.113.24.47]> (raw)
In-Reply-To: <Pine.LNX.4.44.0305150920400.1841-100000@home.transmeta.com>

At 9:53 AM -0700 5/15/03, Linus Torvalds wrote:
>On Thu, 15 May 2003, David Howells wrote:
>  >
>  >   (4) A user has to be able to override the default keyring,
>  >       such that they can, for instance, perform operations
>  >       on a remote filesystem with a different credential.
>
>I disagree. Your (4) comes from your (1) - inability to have
>multiple keyrings. If you have multiple keyrings, you don't
>"override" anything.   You just have a stacking order (ie the
>credentials is a _sorted_ list of  keyrings), and you search
>the credentials for valid keys in order.

I am not completely sure what David meant.  I think I agree
with what he meant, but would argue with your assumption.

A process can be both drosehn@rpi.edu and gad@umich.edu at
the same moment.  By being drosehn@rpi.edu, I'm also in any
number of AFS groups at RPI (a number that I have no knowledge
of or control over).

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

The above says linus@rpi.edu should have absolutely no access to
the file, no matter what AFS or unix groups he is in.  At the same
time, drosehn@rpi.edu has complete access to the file.  If the
process claims to be both of those users, then what is open()
to do?  In the pure-unix world, is a process both userid linus
and userid drosehn?  No.  (it might have different values for
userid and effectiveUserid, but it only has one value for userid
and only one value for effectiveUserid).

You could argue that open() should give access, or that it should
not give access, but my point is that the limitation against being
multiple AFS users at a single time is to avoid that question.
It was not the side-effect of some other decision.

*1 = Actually, in afs the permissions are on a directory level,
      but I'd agree that they *should* be on the file level, and
      thus I said it that way...

-- 
Garance Alistair Drosehn            =   gad@gilead.netel.rpi.edu
Senior Systems Programmer           or  gad@freebsd.org
Rensselaer Polytechnic Institute    or  drosih@rpi.edu

  reply	other threads:[~2003-05-15 23:01 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   ` Garance A Drosihn [this message]
2003-05-16  0:46     ` [OpenAFS-devel] " Russ Allbery
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='p05210620bae9cce008ed@[128.113.24.47]' \
    --to=drosih@rpi.edu \
    --cc=dhowells@redhat.com \
    --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®