Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH

Resolving Hashed Host Keys

Tectia Client includes a tool to resolve which hashed host key belongs to which server. As there can be several server host keys stored on the client-side host, and the file name does not show the server name, it is sometimes necessary to check if a certain server public key is stored on the client host.

In Tectia Connections Configuration GUI, the tool is available on the Host Keys page. See Managing Host Keys.

On the command line, the command syntax is:

ssh-keygen-g3 -F host_name[#port]

For example:

ssh-keygen-g3 -F examplehost#222

The host_name can be the fully qualified domain name, short host name, or the IP address of the remote host. The port definition is optional in the command. If no port is given, the default Secure Shell port 22 is assumed.

The tool shows the location, fingerprint (in the SSH babble format) and type (RSA or DSA) of the requested host's public key or keys. For example:

ssh-keygen-g3 -F examplehost
Fingerprint for key 'examplehost':
  (from location
   /home/user44/.ssh2/hostkeys/keys_bf53882dc47bb767edf161a4f636917f8358d635)
xuvin-zitil-ducid-gevil-vysok-buviz-nynun-pinat-tylev-gusez-dyxix (RSA)

If no keys are found for the given server, the ssh-keygen-g3-F command will report where it looked for the keys, and will conclude as follows:

/ No keys found from any key directories or known_hosts files.

You can define several file locations to be checked for host keys. For more information, see Using the OpenSSH known_hosts File.

===AUTO_SCHEMA_MARKUP===