![\"SSH\"](\"images/colorbar_blue.png\") ![](\"images/logo_ssh_nega.png\"){kind=logo} |
![\"Home\"](\"images/home.gif\") ![](\"images/index.gif\") ![\"Prev\"](\"images/prev.gif\") ![\"Up\"](\"images/up.gif\") ![\"Next\"](\"images/next.gif\") |
When the host key is received during the first connection to a remote host (or when the\n host key has changed) and you choose to save the key, its file name is stored in hashed\n format, keys_hhh..., where hhh is a hash of the\n host port and name. The saved file contains a hash of the host's public key. A salt is\n included in the hash calculations. The value of the salt is stored in the file\n salt in the same directory as the host keys\n ($HOME/.ssh2/hostkeys on Unix,\n %APPDATA%\\SSH\\HostKeys on Windows). The hashed\n host key format is a security feature to make address harvesting on the hosts\n difficult.
In the plain (traditional) format, the name of a host key file includes the host's name\n and port, as in key_22_host.example.com.pub, and the file contains the\n host's public key in plaintext format.
The storage format can be controlled with the filename-format\n attribute of the known-hosts element of the\n ssh-broker-config.xml configuration file. The attribute value must be\n plain or hash (default).
<known-hosts path=\"$HOME/.ssh2/hostkeys\" filename-format=\"plain\" />\n
If you are adding the keys manually, the keys should be named with the\n key_<port>_<host>.pub pattern, where\n <port> is the port the Secure Shell server is running on\n and <host> is the host name you use when connecting to the\n server (for example, key_22_alpha.example.com.pub).
If both the hashed and plaintext format keys exist, the hashed format takes\n precedence.
Note that the host identification is different based on the host name and port the\n client is connecting to. The host name can occur in four different formats:
Fully qualified domain name (FQDN)
Short host name
IPv4 address
IPv6 address
The host key for each name format has to be saved separately, as they are not mutually\n exchangeable.
The host key is saved under the host name format used in the login. For example, if you\n want to use all the host name formats when connecting to a remote host named\n alpha, connect to the host first with the following commands\n and save the host key under all four names:
sshg3 user@alphaproduces the key with the short host name (in plain format\n
key_22_alpha.pub)sshg3 user@alpha.example.comproduces the key with FQDN (in plain format\n
key_22_alpha.example.com.pub)sshg3 user@10.1.101.10produces the key with IPv4 address (in plain format\n
key_22_10.1.101.10.pub)sshg3 user@fd00:10:1:103::1:2f69produces the key with IPv6 address (in plain format\n
key_22_fd000010000101030000000000012f69.pub)
When connecting to a server using its IPv6 address, the IPv6 address given to\n Tectia Client is canonicalized without the colons, and the canonical format is used in the\n known host key file name. For example, the plain format host key file for\n ::1#10022 would be\n key_10022_00000000000000000000000000000001.pub. The canonical format\n is also used in the process of saving and reading hashed host keys.
Also if you need to connect to the same host but different port, your client needs a\n separate host key for that purpose; for example key_22_alpha.pub\n and key_222_alpha.example.com.pub.
After the first connection, the locally stored information about the server public key\n will be used in server authentication.
| |
\n Copyright ![](\"images/copyright.gif\")
2020 SSH Communications Security Corporation
\n This software is protected by international copyright laws. All rights reserved.
Contact Information