From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f1d0367d8c239b5063004f3b4cb3a884@snellwilcox.com>
From: plan9fans@ntlworld.nospam.com
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] auth_proxy: write fd: file does not exist
Date: Mon, 29 Mar 2004 23:02:53 +0100
Topicbox-Message-UUID: 46547c36-eacd-11e9-9e20-41e7f4b1d025

Hi

I am trying to get a single machine to
serve CPU/fossil/venti/auth.

Venti and fossil are happy.

keyfs seems OK - If I boot my terminal standalone
auth/debug to the server is happy with both my
username and bootes.

The secstore seems to work - put and get are OK and
when I network boot a terminal off the server I can
see a GET of 'factotum'.

The secstore contents is correct, I use the same
list of keys cat'ed int /mnt/factotum/ctl on my
standalone terminals.

All the below give the correct results, though
auth/debug checks them implicitly I beleive.
	ndb/ipquery ip xx.xx.xx.xx auth
	ndb/ipquery ip xx.xx.xx.xx fs
	ndb/ipquery ip xx.xx.xx.xx cpu
	ndb/ipquery authdom mydom.com auth

BUT

When I try to boot from the server (pulling only
9load from the terminals hard drive), the kernel loads
(even bootp is OK), I enter my username and secstore
password and get:
	Version...
	Authentication failed (auth_proxy write fd: file does not exist), trying anyways.

	[panic and stackdump]

Other very suspicious symptom is that cpu from a
standalone terminal to the server also fails (even though
auth/debug is happy).

	cpu -h felix
	cpu: can't authenticate: felix: auth_proxy rpc write: cpu: srvauth:: auth server protocol botch

Pointers?

-Steve