From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon, 19 Jun 2000 17:54:37 -0700
Message-Id: <200006200054.RAA10919@ohio.river.org>
From: "Russ Cox" <rsc@plan9.bell-labs.com>
Subject: Re: [9fans] chown - ?
To: 9fans@cse.psu.edu
Topicbox-Message-UUID: c4c18802-eac8-11e9-9e20-41e7f4b1d025

	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