From: Ish Rattan <ratta1i@mail.cmich.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu/auth server
Date: Thu, 6 Jul 2000 15:51:10 +0000 [thread overview]
Message-ID: <3964A4DB.D77E8246@mail.cmich.edu> (raw)
In-Reply-To: <200007051751.SAA19959@pc095.cs.york.ac.uk>
ianb@cs.york.ac.uk wrote:
> Sorry to keep pestering, but I am going to get this
> machine set up as a cpu/auth server, one way or another...
>
> Trying to add a user to the key database: permission denied error
> on the Securenet database. Does keyfs need to be run twice, once
> for the plan9 database and again for the securenet database?
>
> I have tried running it twice ( s/keys/netkeys/ on the args.)
> and it allows addition of users, but will not allow them to connect
> using telnet --- after entering the user, I get
> an "authentication failure" error (and don't get a challenge).
>
Did you make auth=xxxx entry in /lib/ndb/local?
hth
next prev parent reply other threads:[~2000-07-06 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 17:51 ianb
2000-07-06 15:51 ` Ish Rattan [this message]
2000-07-07 11:20 ianb
2001-06-01 19:19 Ish Rattan
2001-06-01 22:32 Wolfgang Helbig
2001-06-01 23:51 ` Ish Rattan
2002-02-07 21:05 Ish Rattan
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=3964A4DB.D77E8246@mail.cmich.edu \
--to=ratta1i@mail.cmich.edu \
--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).