My comment the other day about how I didn’t understand SSH encryption or key types very well got me thinking that maybe it’s something that I should understand a bit more.
It tests both hosts and clients. You either give it the
host:port to scan, or run it as a server and when a client connects it will print information about the encryption schemes supported by the client. It is not particularly reassuring when you see this printed in your terminal:
-- [fail] using elliptic curves that are suspected as being backdoored by the U.S. National Security Agency
There are some hardening guides for host and client configs for various distros—to be honest I would have rather just looked at an example config, rather than running a huge command that uses
sed to edit what it expects to be in there. The huge commands did work, and the client guide even translated over to MacOS.
After a quick test connecting from various devices, I don’t seem to have cut off access for anything. I was able to:
- Connect to my Synology DS420j (which has SSH security set to “High”)1
- Connect to Ubuntu Server 22.04 from:
- Push to GitHub
Of course the best bit is that
ssh-audit is written in Python—so I was expecting to go through
pip hell—BUT it has a Docker image that you can run instead:
$ podman run -it -p 2222:2222 docker.io/positronsecurity/ssh-audit host-to-check:port
So there’s basically no excuse not to just give it a quick check and make sure you’re up to snuff.