From: Hugo Santos <hugo_santos@users.sourceforge.net>
To: 9fans@cse.psu.edu
Subject: [9fans] auth failure
Date: Fri, 13 Jun 2003 20:25:18 +0100 [thread overview]
Message-ID: <C44D2C40-9DD4-11D7-B477-000A9579613E@users.sourceforge.net> (raw)
Hello,
I just setuped a Plan9 CPU Server and was trying to connect to it using
drawterm, but the authentication always fails. In plan9 i get the
following in /sys/log/auth:
... tr-fail authid 192.168.1.12
... tr-fail hostid hugo(192.168.1.12)
... tr-ok hugo@hugo(192.168.1.12) -> hugo@hugo
... tr-ok bootes@bootes(192.168.1.12) -> bootes@bootes
I first tried to login using a user named 'hugo' which i created, but
drawterm told me '?no match', then i tried with bootes, which hangs the
login process, drawterm is still running and i can input text, but i
dont get any more user prompts.
Any ideas on what i've might been doing wrong?
Hugo
next reply other threads:[~2003-06-13 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 19:25 Hugo Santos [this message]
[not found] <Pine.LNX.4.44.0306131517560.15978-100000@fbsd.cpsc.ucalgary.ca>
2003-06-13 21:32 ` Hugo Santos
2003-06-13 21:38 ` boyd, rounin
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=C44D2C40-9DD4-11D7-B477-000A9579613E@users.sourceforge.net \
--to=hugo_santos@users.sourceforge.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).