From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: References: <3faf16ec97ee51a3baa4064d9823cd9f@9netics.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Paul Lalonde Subject: Re: [9fans] Broken auth after replica/pull Date: Sat, 12 May 2007 12:52:37 -0700 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: 66fbaaea-ead2-11e9-9d60-3106f5b1d025 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm an idjit. cpurc.local gets run *long* before it should try listening...That would be the *wrong* place to put the aux/listen commands for your auth server. ty fgb. Paul On 12-May-07, at 9:46 AM, Paul Lalonde wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm pointing the drawterm at the correct auth/cpu servers, both > p9cpu, and I'm getting a connection. > > auth/debug tells me "cannot decrypt ticket1 from auth serve (bad > t.num=0x3a)" > > Still digging. I'll be in China soon. > > Paul > > On 12-May-07, at 12:37 AM, Skip Tavakkolian wrote: > >> what's in the startup script for -a/-c? >> >>> I'm getting to add myself into set of people who have botched their >>> latest pull. But I think I might have done it in a novel way. >>> When I try to drawterm in I get "?password mismatch with auth >>> server"; I've reset my password (auth/changeuser), I've echoed ok >>> to / >>> mnt/keys/plalonde/status, and still, no joy drawterming. >>> One thing is different though. At some point I had a few of the >>> variables in /rc/bin/cpurc.local set to "paulhome.net" instead of my >>> previous "p9cpu"; realizing the error of my ways, I put those >>> back to >>> p9cpu, but my drawterm upon connecting asks for my >>> plalonde@paulhome.net password. I've been unable to find this >>> string >>> anywhere in my config files anymore, and have rebooted the cpu >>> server >>> and restarted the drawterm. Could this (instead of plalonde@p9cpu) >>> be the source of my grief? Is there a way to fix it? >>> >>> Thanks, >>> Paul (who knows better than to upgrade, but was seduced by / >>> power64/... ) >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > > iD8DBQFGRe9XpJeHo/Fbu1wRApIqAJ9NWQlJuRWBjHRWlnCzPnGqK9uYowCg3iCG > G2hqovyM3Adq2elQlNJIR8Y= > =c18+ > -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGRhsGpJeHo/Fbu1wRAosOAJ46peE7lb4uJxc+gNHNMkodlaiXnACfaj1p cWdYsWQ8zb2sNl7h9MTQcv0= =diMk -----END PGP SIGNATURE-----