From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] chown - ?
Date: Mon, 19 Jun 2000 17:54:37 -0700 [thread overview]
Message-ID: <200006200054.RAA10919@ohio.river.org> (raw)
And I got a pair of key files belonging to 'glenda.sys' in common
directory /sys/lib/ssh/
So, the question is how about another (real) users that might log on to
the same terminal host ? How to make them use the same host keys ?
You don't need to be able to read
the secret key -- it just has to exist.
I'm not exactly sure why that is, but
I suspect it's an artifact of having the
server and client compile from the same
libraries.
The host secret key is only used when
running as a server; the protocol never
touches it when running as a client,
except to do RSA_RHOSTS authentication,
which we don't support.
You can generate keys for yourself
by using aux/ssh_genkey $home/lib/ssh
and that will create ssh.secret, ssh.public,
and ssh.public10 (suitable for sharing with
Unix systems). See the ssh man page for more.
Russ
next reply other threads:[~2000-06-20 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-20 0:54 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-19 13:27 Russ Cox
2000-06-19 8:41 Wladimir Mutel
2000-06-19 8:41 Wladimir Mutel
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=200006200054.RAA10919@ohio.river.org \
--to=rsc@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).