11–18 of 18 posts
> Mozilla Guidelines to Secure [Secure Shell]
Could also be a verb ("Guidelines [on how] to Secure Secure Shell") but even as an adjective it makes sense. "Guidelines to [a] Secure [setup of] Secure Shell" is a reasonable way to shorten that sentence, just like "Guide to [writing] Fast Java [code]" would be.
Secure Secure Shell?
What are some other high quality “harden your server” guides? Many seem to be out of date
It doesn't address the Trust On First Use (TOFU) issue.
Secure Secure Shell?
The guide is outdated if you rely on the latest version of OpenSSH. You must update such guides with every new version of OpenSSH. Adding legacy configuration to your OpenSSH config files can even result in a false sense of security (e.g., if the server/client just skip the legacy part and you think it adds some protection). Newer options to secure OpenSSH are also missing (e.g., using U2F for 2FA, introduced in Open…
Are there any updated guides you’re aware of that you could share?
What are some other high quality “harden your server” guides? Many seem to be out of date
They're updated fairly regularly. However, take them with a grain of salt.
They'll worry about things like TCPWrappers, but that's how we did firewalls before they existed. Needless in the days of iptables, ebtables, nftables, etc.
Blogs tend to be recycled/dated recommendations with none/very little third party testing.
What are some other high quality “harden your server” guides? Many seem to be out of date
CIS workbenches are updated regularly. You have to sign up for an account, which is free, to get access.
I don't disagree, they make some good suggestions - but take TCPWrappers for example. CIS will suggest you use it.
That predates firewalls, and requires applications be built/linked against the library.
These days, not worth the time/effort. Do the default-drop policy they suggest, and carry on!