RE: [9fans] auth on terminal

["Tiit Lankots" <t.lankots@aprote.ee>]

> -----Original Message-----
> From: 9fans-admin@cse.psu.edu 
> [mailto:9fans-admin@cse.psu.edu]On Behalf Of 
> plan9fans@ntlworld.nospam.com
> Sent: Thursday, March 25, 2004 5:45 PM
> To: 9fans@cse.psu.edu
> Subject: [9fans] auth on terminal
> 
> 
> Thanks for the help guys but I'am still not there.
> 
> >...then your factotums are nonpersistent.
> My factotum's state is sort-of persistant as I run 
> 	auth/aescbc -d < /n/cdrom/secrets | read -m > /mnt/factotum/ctl
> in my profile to populate it.
> 
> > ...keyfs and authsrv in the same namespace,
> During my attempts to run auth/keyfs it was in the same namespace
> as aux/listen, they where started on the command line in a Rio window.
> 
> >...nvram setup + factotum -S should solve your problems.
> If I run factotum -S and populate it then I guess it would stop
> the password prompts from behind rio (I have not tried, see below).
> 
> > ..-- auth/debug is your friend
> If I don't run the authserver then auth/debug says I have a problem,
> however if I do run the auth server it is happy, on bowth systems. 
> 
> However I now think I don't need an auth server as all I want
> is a direct connection between two machines, both running as me.
> 
> I tried turning on factotums debug but the issue wasn't "obvious"
> Again I did:
> 
> 	cpu -h paris
> 	!Adding key: proto=p9sk1 dom=quintile.net
> 	user[steve]: 
> 	!Adding key: proto=p9sk1 dom=quintile.net
> 	user[steve]: 
> 	...
> 
> Factotum debug from larch
> 
Whaddayaknow, man pages + source can be really informative :)

It turns out that factotum is not used on the auth server at all. 
Authsrv uses keyfs to get to it's auth data.
Keyfs database (/adm/keys) is encrypted with the server's key,
stored in nvram.

So you'll need to
1. auth/wrkey (if you don't want to type a password each startup), or
2. run auth/keyfs -p in termrc (this prompts for password)

The 'Configuring a Standalone CPU Server' page in Wiki gives a 
decent rundown.