From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200703212303.l2LN3Vl25960@zamenhof.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? In-reply-to: Your message of "Mon, 19 Mar 2007 14:47:42 +0100." <200703191347.l2JDlgt09152@zamenhof.cs.utwente.nl> References: <200703191347.l2JDlgt09152@zamenhof.cs.utwente.nl> From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25958.1174518211.1@zamenhof.cs.utwente.nl.cs.utwente.nl> Date: Thu, 22 Mar 2007 00:03:31 +0100 Topicbox-Message-UUID: 2b7308ba-ead2-11e9-9d60-3106f5b1d025 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.