9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] v9fs question
Date: Mon, 13 Jul 2009 09:51:50 -1000	[thread overview]
Message-ID: <Pine.BSI.4.64.0907130942140.5249@malasada.lava.net> (raw)
In-Reply-To: <f158dc670907130808g6ecfdf44ncf3f4b3b82c1b611@mail.gmail.com>

> Adding the support we had before the access= support is probably easy,
> but I would like to make it better and support authentication for
> multiple users. Still no idea what is the correct way. :( Any
> suggestions are welcome.

I'm glad you brought this up because this is a conversation I wanted
to see.  I can think of several different ways to go about
this:


    - nfs style: if you authenticate to the remote as root,
      you can speak for any of the uids you want to.  This
      assumes a common mapping of users to uids across
      the machines.
      twist: root squash as an option, as per nfs.

   - single user:  All files are presented as if owned by
     a single user.  This need not be the user that was
     authenticated on the remote side.  Any local user id
     would work.  Perm checks are going to be done twice,
     anyway.  Once locally (based on perms + the user id
     assigned to all files) and once remotely (on file server)
     based on the remote's idea of what user id you are (who
     you authenticated as).

   - multi-user authentication:  A separate authenticated 9p
     channel is opened for each user that makes a request over
     the remote mount.  This requires that some daemon have
     access to credentials to authenticate each user at least
     once.  This daemon could be set up in advance or it could
     interactively request auth info as it goes.  I think
     one obvious approach is to prime it with creds for a bunch
     of accounts and have it fall back to the "single user"
     case for all other accounts -- by mapping to some distinguished
     user such as "nobody" or "guest" or "unauth9p".

by the way, I think auth method offers some room for thought
here, too.  When talking with plan9 or inferno then p9sk1
or the inferno auth (whose name I forget) is the obvious choice.
However, when talking just between several non-plan9 machines
(ie. linux-linux) then other auth choices might make sense.
How many 9p servers actually use auth?  Most "file servers"
are only accessed remotely through "cpu" or locally without
auth, right?

>    Lucho

Tim Newsham
http://www.thenewsh.com/~newsham/



  reply	other threads:[~2009-07-13 19:51 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 18:46 Tim Newsham
2009-07-11 18:50 ` Eric Van Hensbergen
2009-07-11 19:03   ` Tim Newsham
2009-07-11 19:47     ` Eric Van Hensbergen
2009-07-11 20:03     ` J.R. Mauro
2009-07-12  3:19       ` Uriel
2009-07-13  8:24     ` sqweek
2009-07-13  8:51       ` hiro
2009-07-13 14:20       ` Eric Van Hensbergen
2009-07-13 20:44         ` hiro
2009-07-13 21:45           ` hiro
2009-07-13 22:05             ` Eric Van Hensbergen
2009-07-13 22:18               ` J.R. Mauro
2009-07-13 23:16                 ` ron minnich
2009-07-13 23:22                   ` Eric Van Hensbergen
2009-07-13 23:37                     ` ron minnich
2009-07-13 23:47                       ` Eric Van Hensbergen
2009-07-13 23:41                   ` J.R. Mauro
2009-07-13 23:50                     ` erik quanstrom
2009-07-14  0:00                       ` J.R. Mauro
2009-07-14  0:06                         ` erik quanstrom
2009-07-14  0:01                     ` Eric Van Hensbergen
2009-07-14  0:08                       ` ron minnich
2009-07-14  0:46                         ` J.R. Mauro
2009-07-14  0:42                       ` J.R. Mauro
2009-07-14  0:58                         ` Eric Van Hensbergen
2009-07-14  1:28                           ` Latchesar Ionkov
2009-07-14  1:35                             ` Devon H. O'Dell
2009-07-14  2:05                             ` Tim Newsham
2009-07-14  0:42                   ` Tim Newsham
2009-07-14  0:50                     ` erik quanstrom
2009-07-14  0:56                     ` Eric Van Hensbergen
2009-07-14  4:51                     ` lucio
2009-07-14  4:29                 ` lucio
2009-07-14  4:26               ` lucio
2009-07-13 22:00           ` Eric Van Hensbergen
2009-07-14 19:05         ` sqweek
2009-07-14 20:11           ` Eric Van Hensbergen
2009-07-13 14:59       ` lucio
2009-07-13 15:04         ` Eric Van Hensbergen
2009-07-13 15:08       ` Latchesar Ionkov
2009-07-13 19:51         ` Tim Newsham [this message]
2009-07-14  7:34         ` sqweek
2009-07-14 11:08           ` roger peppe
2009-07-14 11:20             ` hiro
2009-07-14 12:48             ` Eric Van Hensbergen
2009-07-14 15:45             ` ron minnich
2009-07-14 16:31             ` Tim Newsham
2009-07-14 20:21               ` roger peppe
2009-07-14 13:10           ` Eric Van Hensbergen
2009-07-14 13:23             ` erik quanstrom
2009-07-14 14:26               ` Eric Van Hensbergen
2009-07-14 14:44                 ` erik quanstrom
2009-07-14 14:33           ` Latchesar Ionkov
2009-07-14 14:54             ` Eric Van Hensbergen
2009-07-14 15:01               ` erik quanstrom
2009-07-14 15:13                 ` Eric Van Hensbergen
2009-07-14 15:19                   ` erik quanstrom
2009-07-14 15:37                     ` Eric Van Hensbergen
2009-07-14 16:12                       ` erik quanstrom
2009-07-14 16:19                         ` Eric Van Hensbergen
2009-07-14 15:06               ` Latchesar Ionkov
2009-07-14 15:48                 ` ron minnich
2009-07-14 15:59                   ` Eric Van Hensbergen
2009-07-14 14:37           ` Latchesar Ionkov

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=Pine.BSI.4.64.0907130942140.5249@malasada.lava.net \
    --to=newsham@lava.net \
    --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).