9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9any auth in u9fs: uid value in ticked is ignored
Date: Mon, 10 Oct 2011 17:18:56 +0100	[thread overview]
Message-ID: <CAOw7k5hcQUCB-CgwCNAc2+_5ggTUeVwcJX4oSR3TkCdAwUu0gw@mail.gmail.com> (raw)
In-Reply-To: <CAG3N4d-PT7+aj4ZU5=YpCk9eDnxT76TGLE5uWCqSfsSEfOoGZA@mail.gmail.com>

Indeed the whole point of Tauth is that the uname in Tattach isn't intended to
be trusted on its own, unless supported by an afid that attests to a previous
authentication of the uname. (An exception is that many servers only
run as the invoking user
and don't insist on authentication.) That's the documented protocol.

It seems that the servers you mention substitute t.cuid at the attach,
but that makes uname relatively pointless: it might just as well not
be provided in Tauth since it's effectively ignored. It would be
needed in Tattach in case there is no Tauth,
but is also effectively ignored in Tattach if there were a Tauth. (In that case,
who cares if the two strings are the same if they are irrelevant?
What's the point of the server checking?)
That isn't the documented protocol.

I'm ignoring the devmnt aspect because that's outside the protocol as such.
I'm interested in what servers ought to be doing (or perhaps whether
the protocol should be change).



  reply	other threads:[~2011-10-10 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 12:07 Yaroslav
2011-10-10 12:39 ` Charles Forsyth
2011-10-10 14:01   ` Yaroslav
2011-10-10 16:18     ` Charles Forsyth [this message]
2011-10-10 20:47       ` Yaroslav
2011-10-10 22:03         ` Charles Forsyth

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=CAOw7k5hcQUCB-CgwCNAc2+_5ggTUeVwcJX4oSR3TkCdAwUu0gw@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --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).