It’s scary month
A key-based SSH login could not be relayed this way.
There is no good reason to use ssh with a password. Always use key based authentication.
Here is a tutorial for anyone who may need it. https://www.digitalocean.com/community/tutorials/how-to-create-ssh-keys-with-openssh-on-macos-or-linux
Totally agree. Better still, don’t expose OpenSSH directly to the internet. It’s just too popular at this point and boasts way too many features. The pressure to break it is overwhelming. Layer your defences. You can use a VPN like IPSec, Wireguard, or Tailscale or even something as simple as spiped and you can configure OpenSSH’s client with ProxyCommand to make it completely transparent. It’s not that these won’t have holes also, but hopefully not at the same moment OpenSSH has something.
I have OpenSSH on a server (key not pw). But I UFW everything except my own IP into the void on that port.
My IP is semi static from my ISP. It changes, but like once every couple years. My thinking is that an attacker would need some exploit to bypass UFW packet filtering and the OpenSSH vuln. Which would hopefully be enough to keep me safe if/when that ssh vuln hits.
Agreed. Great additional and needed information that I neglected to mention.
Is it only standard port though?
Yeah port 22 only.
