From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <5921df734e5f770862e672cb104f1e4f@9netics.com> References: <5921df734e5f770862e672cb104f1e4f@9netics.com> Date: Tue, 12 Jan 2010 00:10:41 -0200 Message-ID: <32d987d51001111810y7085b6e0td0922d2aacc52968@mail.gmail.com> From: "Federico G. Benavento" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] mysterious auth Topicbox-Message-UUID: bde16ad6-ead5-11e9-9d60-3106f5b1d025 are you sure that the passwords in nvram and auth/changeuser do match for bootes? On Mon, Jan 11, 2010 at 8:22 PM, Skip Tavakkolian <9nut@9netics.com> wrote: > on a new network and standalone auth+fs (built from CD image of Jan > 7th), auth is refusing to concur. =C2=A0i've used Russ' message from a > while back [1] as a checklist. =C2=A0auth/debug reports: > > =C2=A0 =C2=A0 =C2=A0 =C2=A0cannot decrypt ticket1 from auth server (bad t= .num=3D0x...) > =C2=A0 =C2=A0 =C2=A0 =C2=A0auth server and you do not agree on key for bo= otes@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. =C2=A0it's > interesting that reading /mnt/factotum/ctl also gives "no key > matches/failure no key matches" message along with the key. =C2=A0key loo= ks > like this: > > key proto=3Dp9sk1 dom=3Dbta.somedomainx.org user=3Dbootes !password? > > i've tried logging in from a term (pxeloaded from the same auth+fs) > with similar results. =C2=A0in that case factotum debug says "no key > matches proto=3Dp9sk1 role=3Dserver dom?". =C2=A0this 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/797= bce6a973b84e8/0941aa4593f9dc73?lnk=3Dgst&q=3Dfactotum+nvram#0941aa4593f9dc7= 3 > > > --=20 Federico G. Benavento