From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Broken auth after replica/pull
Date: Sat, 12 May 2007 12:52:37 -0700 [thread overview]
Message-ID: <A3943AE1-405F-4531-99F3-ABAC09BD494F@telus.net> (raw)
In-Reply-To: <AACC9F4F-150A-4ACC-816F-D29512B3A2D9@telus.net>
-----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-----
next prev parent reply other threads:[~2007-05-12 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 7:24 Paul Lalonde
2007-05-12 7:36 ` Federico Benavento
2007-05-12 16:02 ` Paul Lalonde
2007-05-12 16:25 ` lucio
2007-05-12 7:37 ` Skip Tavakkolian
2007-05-12 16:46 ` Paul Lalonde
2007-05-12 19:52 ` Paul Lalonde [this message]
2007-05-12 10:19 ` Martin Neubauer
2007-05-12 16:44 ` Paul Lalonde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A3943AE1-405F-4531-99F3-ABAC09BD494F@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).