9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] factotum/802.1x catch 22?
Date: Thu, 22 Mar 2007 00:03:31 +0100	[thread overview]
Message-ID: <200703212303.l2LN3Vl25960@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Mon, 19 Mar 2007 14:47:42 +0100." <200703191347.l2JDlgt09152@zamenhof.cs.utwente.nl>

I wrote, at the end of a description of a scenario
where factotum needs to be started before the network
is configured, to aid in enabling the network access,
such that it cannot do those things it normally
does during startup, like accessing secstore:

> I have been thinking about additional factotum ctl
> messages to essentially give it some time later
> stuff that was not available when it was started, like
>  - the equivalent of '-a authaddr' command line
>  - tell it to try to access secstore
> to be able to have just a single instance of factotum
> running, but I'm not sure that would be the way to go...

I tried that to see if it would work. it does.

I've extended my factotum with an 'authaddr' ctl verb.
(don't know wat can of worms it opens...)
reseiving it it will also trigger an attempt to access
secstore if it wanted to do that on startup but couldn't
(like because there was no network configured yet.)

I adapted my boot.c to start factotum before the root fs access
method is configured, such that, if config of root fs access
method needs factotum to handle keys to enable the network,
factotum will be there.
after config of the root fs access method authaddr is passed
on to the running factotum, if it was set.

Axel.


  parent reply	other threads:[~2007-03-21 23:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 13:47 Axel Belinfante
2007-03-20 13:44 ` erik quanstrom
2007-03-21 23:03 ` Axel Belinfante [this message]
2007-03-22  4:38   ` lucio
2007-03-22  5:19     ` Uriel
2007-03-22  6:13       ` Noah Evans
2007-03-22  9:11     ` erik quanstrom
2007-03-22 15:31       ` Joel C. Salomon
2007-03-25 11:56     ` Axel Belinfante
2007-03-25 12:12       ` Uriel
2007-03-25 14:48         ` lucio
2007-03-25 20:38           ` Charles Forsyth
2007-03-26  6:51             ` lucio
2007-03-27  9:24               ` Charles Forsyth
2007-03-27 17:29                 ` lucio
2007-03-25 15:40         ` erik quanstrom
2007-03-25 16:44           ` lucio
2007-03-25 20:15           ` Axel Belinfante
2007-03-25 14:46       ` lucio

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=200703212303.l2LN3Vl25960@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --cc=9fans@cse.psu.edu \
    /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).