From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <002bf53ac20d8f0efa1bf7d1afb584c4@plan9.bell-labs.com>
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu server auth problems
In-Reply-To: <20030111122143.I85448-100000@fbsd.acl.lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Sat, 11 Jan 2003 16:18:20 -0500
Topicbox-Message-UUID: 3e4b8cac-eacb-11e9-9e20-41e7f4b1d025

run auth/debug and you'll find that your ndb setup
is not quite correct.  in particular, the cpu server
doesn't know how to find the authserver for authdom=plan9box.

all the situations that you've described as working
do so because they don't require the client side
to know how to find the auth server: for netkey
the server side takes care of it, for cpu as bootes
factotum can make up some tickets by itself, and
for the boot-from-file-server, factotum gets the ip address
then and uses it as a fallback.