From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5921df734e5f770862e672cb104f1e4f@9netics.com>
To: 9fans@9fans.net
Date: Mon, 11 Jan 2010 14:22:08 -0800
From: Skip Tavakkolian <9nut@9netics.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] mysterious auth
Topicbox-Message-UUID: bdd67144-ead5-11e9-9d60-3106f5b1d025

on a new network and standalone auth+fs (built from CD image of Jan
7th), auth is refusing to concur.  i've used Russ' message from a
while back [1] as a checklist.  auth/debug reports:

	cannot decrypt ticket1 from auth server (bad t.num=0x...)
	auth server and you do not agree on key for bootes@bta.somedomainx.org

factotum debug output says "no key matches"; factotum has the right
key and i've zero'ed nvram a couple of times to be sure.  it's
interesting that reading /mnt/factotum/ctl also gives "no key
matches/failure no key matches" message along with the key.  key looks
like this:

key proto=p9sk1 dom=bta.somedomainx.org user=bootes !password?

i've tried logging in from a term (pxeloaded from the same auth+fs)
with similar results.  in that case factotum debug says "no key
matches proto=p9sk1 role=server dom?".  this last message looked a bit
weird and when i check /dev/hostdomain, it is empty.

any ideas?

[1] http://groups.google.com/group/comp.os.plan9/browse_thread/thread/797bce6a973b84e8/0941aa4593f9dc73?lnk=gst&q=factotum+nvram#0941aa4593f9dc73