Bug 1166479 - sshd complaining ' Could not load host key: /etc/ssh/sshhostdsakey'.

  1. # Package generated configuration file # See the sshdconfig(5) manpage for details # What ports, IPs and protocols we listen for Port 22 # Use these options to restrict which interfaces/protocols sshd will bind to #ListenAddress:: ListenAddress 192.168.1.10 ListenAddress 127.0.0.1 Protocol 2 # HostKeys for protocol version 2 HostKey /etc/ssh.
  2. Host keys are just ordinary SSH key pairs. Each host can have one host key for each algorithm. Each host can have one host key for each algorithm. You should get an SSH host key fingerprint along with your credentials from a server administrator in order to prevent man-in-the-middle attacks.

Get Ssh Host Key Fingerprint

Generate Etc Ssh Ssh_host_dsa_key

SSH allows the use of encryption keys to be used to allow logging into a system instead of having to remember a plain text password.
This is great for use in scripts, and automated tasks, but can be a problem is anyone else ever gets the keys somehow.
If the keys become compromised, you must generate new SSH keys.
With the increasing use of virtual servers nowadays, if you are creating new servers based on a image file/backup, you may find the new server has the same keys as the original. You should generate new SSH keys on the new server if that is the case.
Generate new SSH keys:

Restart the SSH server for the new keys to take effect.

Generate Etc Ssh Ssh_host_dsa_key

Prevent DNS Amplification Attacks with BIND

August 5, 2013

Generate /etc/ssh/ssh_host_dsa_key

adding persistent static routes on ubuntu

February 1, 2015
Coments are closed
Scroll to top