9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rogelio Serrano <rogelio.serrano@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fsctotum per user instances?
Date: Sun,  7 Apr 2013 19:50:53 +0800	[thread overview]
Message-ID: <CANszf4jjR27hyYLL4TND=Xpb=yN=o8nCTqZ-3J7yVHMdW2kWoA@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5j6mKQKjwDZoMpdamGrJHrpVA_eEHj0s9sJmF7R-2kBvQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

On Apr 7, 2013 4:40 PM, "Charles Forsyth" <charles.forsyth@gmail.com> wrote:
>
> an auth/factotum is started by some initialisation code when you boot and
log in to your terminal.
> on the cpu server, the same is true for the host owner (the owner of the
cpu service),
> but then when you cpu(1) into a cpu server, your profile has a switch on
the service environment variable,
> which is "cpu" for an incoming cpu call:
>
> h% cat $home/lib/profile
> ...
> switch($service){
> case terminal
> ...
> case cpu
> ...
> bind /mnt/term/mnt/factotum /mnt/factotum
> ...
> }
>
> within cpu, the terminal's name space is available at /mnt/term, so it
simply binds the /mnt/factotum
> in that name space onto /mnt/factotum in the cpu server, so you have all
your keys.
>
> Note that this is a simple way in which the use of file servers to
provide system services and resources,
> combined with 9P to import and export them, allows an interesting
function to be provided without having
> any further code or special protocols.

Awesome! Thanks guys!

So the incoming authentication is handled by the cpu owner factotum? That
means the authentication information is held by the cpu owner factotum and
the user factotum just handles the users keys? And the user factotum is run
after authentication.

[-- Attachment #2: Type: text/html, Size: 1581 bytes --]

  reply	other threads:[~2013-04-07 11:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07  3:28 Rogelio Serrano
2013-04-07  5:25 ` a
2013-04-07  8:40   ` Charles Forsyth
2013-04-07 11:50     ` Rogelio Serrano [this message]
2013-04-08  8:52       ` Yaroslav
2013-04-08  9:14         ` Stuart Morrow
2013-04-08  9:19           ` Bence Fábián
2013-04-07 13:05     ` erik quanstrom

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='CANszf4jjR27hyYLL4TND=Xpb=yN=o8nCTqZ-3J7yVHMdW2kWoA@mail.gmail.com' \
    --to=rogelio.serrano@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).