I like secstore, but the chicken-or-egg question is real. It's
from the world where you have a dedicated auth server, and that
doesn't always track with a laptop needing a key to get to the
network. I do store my wpa key outside secstore for this reason,
and then use it for everything else. Still, if you've got a
local filesystem, I think that's all you need to bootstrap.
When I have a system that needs a wpa key, I have this in
my /cfg/sysname/termrc:
echo 'key proto=wpapsk essid=Ranch !password='^`{cat
$home/lib/wpa/Ranch} > /mnt/factotum/ctl
aux/wpa -p2s Ranch /net/ether1
ip/ipconfig -g 10.1.20.1 ether /net/ether1 add 10.1.20.120 255.255.255.0
I also have a script, 'feedkeys', which is just this:
#!/bin/rc
store=your.secstore.here
auth/secstore -s $store -G factotum > /mnt/factotum/ctl
I end up using that script at other times, too, like calls in
from other environments (eg ssh). Then in my $home/lib/profile,
the 'case terminal' clause includes:
if (! test -e /mnt/factotum/ctl)
auth/factotum -a your.secstore.here
feedkeys
With this, networking comes up without my intervention, I get all
my keys in factotum, and I only have to type my secstore password
once (and no others).
------------------------------------------
9fans: 9fans
Permalink:
https://9fans.topicbox.com/groups/9fans/T2e892f330bc0513b-Mdbf9da4fe44462b0ee63272d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
