From: "Federico G. Benavento" <benavento@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mysterious auth
Date: Tue, 12 Jan 2010 00:10:41 -0200 [thread overview]
Message-ID: <32d987d51001111810y7085b6e0td0922d2aacc52968@mail.gmail.com> (raw)
In-Reply-To: <5921df734e5f770862e672cb104f1e4f@9netics.com>
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. 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
>
>
>
--
Federico G. Benavento
next prev parent reply other threads:[~2010-01-12 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 22:22 Skip Tavakkolian
2010-01-11 22:46 ` erik quanstrom
2010-01-12 2:10 ` Federico G. Benavento [this message]
2010-01-12 6:10 ` Skip Tavakkolian
2010-01-22 23:27 ` Skip Tavakkolian
2010-01-23 3:18 ` erik quanstrom
2010-01-23 6:12 ` lucio
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=32d987d51001111810y7085b6e0td0922d2aacc52968@mail.gmail.com \
--to=benavento@gmail.com \
--cc=9fans@9fans.net \
/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).