From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7a5d84be9a54c9d963300461d06c069c@snellwilcox.com>
From: "Steve Simon" <steve.simon@snellwilcox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] auth on terminal
In-Reply-To: <ddd22c46836323d0b698652c4dd10ace@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 25 Mar 2004 14:51:10 +0000
Topicbox-Message-UUID: 422c4f62-eacd-11e9-9e20-41e7f4b1d025

> If you are running as the same user on both systems, you don't even need
> an auth server...
> 
> Keyfs will get the password it encrypts/decrypts the /adm/keys with from
> the nvram parittion if there's anything there (i.e. if you've already
> run wrkeys and put something there).  Otherwise, it will indeed prompt
> with password:.  Did you start it in the background?

I didn't start keyfs in the background, however Richards suggestion
of using
	service=cpu auth/keyfs ...
stopped the prompts for a password; I guess keyfs changes it behaviour
depending.

Perhaps I am beginning to understand, Is it that keyfs is only
needed to change ones identity?

Ok, I scapped keyfs, now I just use aux/listen on the server side.

	larch% cpu -h paris

	!Adding key: proto=p9sk1 dom=mydom.net
	user[steve]: 
	password: 
	!

	!Adding key: proto=p9sk1 dom=mydom.net
	user[steve]:
	password: 
	!

	[ad nausem]

However I do have a key, and the factotums are the same
(the contents transfered securely via Neware :-)

	larch% grep mydom /mnt/factotum/ctl
	key proto=p9sk1 dom=mydom.net user=steve !password?

	paris% grep mydom /mnt/factotum/ctl
	key proto=p9sk1 dom=mydom.net user=steve !password?

only one small step now ...

-Steve