From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] File Server Authentication Woes
Date: Mon, 6 May 2002 21:17:01 -0400 [thread overview]
Message-ID: <4b525679e219ed385b586102c0e7903a@plan9.bell-labs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
The client calls the auth server. If there isn't anything in
/sys/log/auth then the client isn't even trying the auth server.
It seems like the auth server doesn't know where the auth server
is, so to speak.
On the auth server, do
% ndb/csquery
> net!$auth!ticket
If there isn't a translation, that's the problem. There are two
places you can specify the auth server, /net/ndb (plan 9 DHCP supplies
it) or in /lib/ndb/local. Look for 'auth='.
[-- Attachment #2: Type: message/rfc822, Size: 2055 bytes --]
From: Eric Van Hensbergen <evanhensbergen@austin.rr.com>
To: 9fans@cse.psu.edu
Subject: [9fans] File Server Authentication Woes
Date: 06 May 2002 19:57:43 -0500
Message-ID: <1020733065.1790.2.camel@airwick>
I'm having a bit of trouble getting my newly installed file server to
work with my Auth server. I've installed everything from scratch and
have a stand-alone auth server, a stand-alone terminal, and a file
server. Everything seems to be happy-happy except when I go to mount
the file server from the auth-server I get an authentication error.
There doesn't seem to be anything useful in /sys/log/auth about it (or
in any of the other logs). Is there any way I sanity check the auth
server configuration on the file server or get more verbose debugging
about where things are breaking down?
-eric
next reply other threads:[~2002-05-07 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 1:17 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 16:20 rsc
2002-05-07 17:26 ` Eric Van Hensbergen
2002-05-07 15:18 Russ Cox
2002-05-07 15:49 ` Eric Van Hensbergen
2002-05-07 1:03 Russ Cox
2002-05-07 15:10 ` Eric Van Hensbergen
2002-05-07 9:30 ` plan9
2002-05-07 0:57 Eric Van Hensbergen
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=4b525679e219ed385b586102c0e7903a@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--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).