From: YAMANASHI Takeshi <9.nashi@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ssh and standalone cpu/auth server?
Date: Wed, 13 Jul 2005 09:59:16 +0900 [thread overview]
Message-ID: <e2782f38cf6dce7d442d99c89804f180@orthanc.cc.titech.ac.jp> (raw)
> An ssh out of this server to a remote (Linux box) has
> problems..
The factotum started by the kernel doesn't prompt for keys
on a cpu server.
You might want to start another factotum before ssh.
cpu% auth/factotum
cpu% ssh user@remote
--
next reply other threads:[~2005-07-13 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 0:59 YAMANASHI Takeshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 20:47 rattan
2005-07-12 20:54 ` Devon H. O'Dell
2005-07-14 4:34 ` David Leimbach
2005-07-14 5:25 ` Dave Lukes
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=e2782f38cf6dce7d442d99c89804f180@orthanc.cc.titech.ac.jp \
--to=9.nashi@gmail.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).