I am trying to fix my SSH setup on Fedora and RedHat with ssh-audit.

I managed to fix the ciphers and algorithms by setting

KexAlgorithms diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,[email protected]
Ciphers [email protected],[email protected],[email protected],aes256-ctr,aes192-ctr,aes128-ctr
MACs [email protected],[email protected],[email protected]

in /etc/ssh/sshd_config

The audit tool is still complaining about the host keys that should be re-generated:

# host-key algorithms
(key) ecdsa-sha2-nistp256            -- [fail] using weak elliptic curves
                                     `- [warn] using weak random number generator could reveal the key
                                     `- [info] available since OpenSSH 5.7, Dropbear SSH 2013.62
# algorithm recommendations (for OpenSSH 7.9)
(rec) -ecdsa-sha2-nistp256           -- key algorithm to remove 

I then recreated the Diffie-Hellman moduli and generated new keys

rm -fv /etc/ssh/ssh_host_*
ssh-keygen -G moduli-2048.candidates -b 2048
ssh-keygen -T moduli-2048 -f moduli-2048.candidates
cp moduli-2048 /etc/ssh/moduli
ssh-keygen -A

The audit tool is still complaining. How could I use a better random number generator? I can I exclude ecdsa-sha2-nistp256 by the key generation?

  • The link above points to old ssh-audit, the maintained fork is github.com/jtesta/ssh-audit, also available via pip install ssh-audit
    – Tombart
    Commented Oct 20, 2023 at 11:29

2 Answers 2


sshd-keygen@service can be configured with this file:


By default on RHEL8 it has:

[email protected]
[email protected]
[email protected]

If @Matteo would remove the Wants for rsa and ecdsa host keys, then these files won't reappear after restarting sshd.

ssh-audit is happy if you remove from /etc/ssh/sshd_config the lines:

HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key

All of the curves used by ECDSA keys are considered weak. Just delete the ssh_host_ecdsa_key and ssh_host_ecdsa_key.pub files without replacing them, and/or comment out the entries for them in sshd_config. The only kinds of keys worth having are RSA and Ed25519, and you should already have them.

  • It works but they are regenerated each time I start the sshd service. I have to check what is happening there...
    – Matteo
    Commented Nov 16, 2018 at 13:19
  • See if commenting out the entries for them makes sshd stop using them, even if they exist. Commented Nov 16, 2018 at 13:20
  • If I comment them out, they are still re-generated but not used. So fine for me :-)
    – Matteo
    Commented Nov 16, 2018 at 13:21
  • Change the permission to world readable, then sshd will not use them. Commented Jan 18, 2022 at 11:14
  • @bbaassssiiee That seems unwise. The private key could get stolen, and then some unaware sysadmin could later "fix" the permissions. Commented Jan 18, 2022 at 14:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .