From: Moroo Jun <moroo@nifty.com>
To: 9fans@cse.psu.edu
Subject: [9fans] telnet/ftp auth problems
Date: Mon, 1 Apr 2002 23:18:24 +0900 [thread overview]
Message-ID: <p04320403b8ce17bc3614@[192.168.1.31]> (raw)
I tried to change my plan9 standalone terminal server to cpu/auth
standalone server as this page.
http://plan9.bell-labs.com/wiki/plan9/32/index.html
(http://plan9.bell-labs.com/wiki/plan9/7/index.html)
I can access as anonymous user (ftp) or none (telnet). But I can't access
as real user.
localhost% ftp 192.168.1.32
Connected to 192.168.1.32.
220 Plan 9 FTP server ready
Name (192.168.1.32:jun):
331 encrypt challenge, 30569, as a password
Password:
530 Not logged in: permission denied
ftp: Login failed.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp>
/sys/log/auth
nu13d Apr 1 17:38:52 keyfs starting warnings: 3ca8e17c 3ca78f55
nu13d Apr 1 17:38:52 tr-fail hostid (192.168.1.32)
nu13d Apr 1 17:38:52 tr-ok @(192.168.1.32) -> @bootes
nu13d Apr 1 17:51:56 cr-ok jun@bootes(192.168.1.32)
Where should I check?
--
Moroo Jun
next reply other threads:[~2002-04-01 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 14:18 Moroo Jun [this message]
2002-04-01 14:53 Russ Cox
2002-04-02 13:15 ` Moroo Jun
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='p04320403b8ce17bc3614@[192.168.1.31]' \
--to=moroo@nifty.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).