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 [email protected]
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
