3 ms·
Perhaps you have got a good guide how to implement this?
by dzhiurgis 13y ago
Perhaps you have got a good guide how to implement this?
- spindritf 13y agoDoesn't help in this case but in your /etc/ssh/sshd_config or similar change or, if missing, add PubkeyAuthentication yes ChallengeResponseAuthentication no PasswordAuthentication no PermitRootLogin no Make sure you can log in using your key and su/sudo from that unprivileged user before applying those changes.
- dzhiurgis 13y agoThanks, done that.
- antocv 13y agoJust google it, its in the manual as well. But the gist of it is PermitRootLogin no in your sshd_config and Protocol 2 (to disable protocol 1), PubkeyAuthentication yes Password authentication no For this specific vulnerability those will not do, as this exploit is for post-authentication, whether password or pubkey doesnt matter. Hence, you can add Ciphers blowfish-cbc which will only allow that cipher to be used. Also add MACs hmac-sha2-512 to only allow that MAC and none, weaker, others.