From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [9fans] auth on terminal
Message-ID: <81132473206F3A46A72BD6116E1A06AE056176@black.aprote.com>
From: "Tiit Lankots" <t.lankots@aprote.ee>
To: <9fans@cse.psu.edu>
Date: Thu, 25 Mar 2004 17:09:49 +0200
Topicbox-Message-UUID: 424259ce-eacd-11e9-9e20-41e7f4b1d025

> 	larch% cpu -h paris
>=20
> 	!Adding key: proto=3Dp9sk1 dom=3Dmydom.net
> 	user[steve]:=20
> 	password:=20
> 	!

The fact that you see this implies that the local factotum does not=20
have a key for what the remote requests. I think it works this way:
A full-blown auth server runs factotum -S on startup; it (factotum) =
reads
authentication data (which contains the auth domain, among other things)
from nvram and initialises some important data to use this info.

So I guess, nvram setup + factotum -S should solve your problems.