I'm tempted to write a competing article: "If you're using SSH in 2022, you're doing it wrong"
There's no need to open port 22 if tools like AWS Session Manager (and GCP's equivalent) are available to you.
There's no need to open port 22 if tools like AWS Session Manager (and GCP's equivalent) are available to you.
Also, not all servers are on cloud platforms.
Not all servers are on cloud platforms, but there are somewhat comparable ways to shunt a serial or out-of-band management console over the network.
Not that I'd want to either, of course. Bringing an 1988 solution back to fix a conceptual 2022 problem does not sound like a great fix :)
I understand that in some workload types you want to have full autodeployment on servers, using ansible, kerberos, whatever. In that case interactive login is never needed.
But this is a very specific subset of 'servers' in my opinion. A lot of HN contributors work in this so this approach may work for them but it won't everywhere.