asosin writes:
: Secondly there are
: two steps that you need to do in the .ssh2
: a). add the name of the pub_key.pub to the authorization file.
: b). copy the pub_key.pub file to the remote computer.
The use of separate files to hold the keys and the authorization data
is a) clearer and easier to read b) easier to update, as the keyfiles
need only be copied, and the corresponding "authorization" file
updated.
: One question I hope one of you can answer for me is in SSH2 is if there is
: also a \etc\ssh_known_hosts file
: which the administrator can keep updated and then distribute to all the
: clients such that no annoying prompts are give to the users asking them if
: they wish to accept the Public Key. If the user answer yes then the public
: key would then be added to the local machine $HOME$\.ssh\know_hosts file
: ?
:
: How is this handled in SSH2 and what does the Admin have to do ?
: A brief explanation would be appreciated.
The host keys, which are accepted are copied to
$HOME/.ssh2/hostkeys. The equivalent of /etc/ssh_known_hosts in ssh2
is the directory /etc/ssh2/hostkeys, where the hostkeys of known hosts
are copied. ssh2 also uses a directory /etc/ssh2/knownhosts, where the
publickeys, which are trusted for hostbased authetication, are stored.
--
[[EMAIL PROTECTED] -- Sami J. Lehtinen -- [EMAIL PROTECTED]]
[work:+358 9 85657425][gsm:+358 50 5170 258][http://www.iki.fi/~sjl]
[SSH Communications Security Corp http://www.ssh.com/]
