I am fairly glad I have stuck with stock OpenSSH that ships with Linux. This incident proves I am glad with that choice.

Over the decades, I have maintained remote access through port forwarding on my router - at one point in 2008 I put SSH on port 80 so I could access it from the restricted wifi network at the hospital my grandmother was at. I have also used openvpn. I have also used cloudflare tunnels. But in the end, I always connect to hardened openssh with key only authentication.

▲

LeBit 10 minutes ago | parent | next [-]

Doing ssh through port 80 or 53 or 443 is immediately flagged.

I understand port 443 is always opened but nowadays you can’t just run ssh traffic on 443 without it being detected as not being https

▲

octoberfranklin 9 minutes ago | parent [-]

Flagged by who? The Internet Police? This comment is absurd.

	▲	novafunc 2 minutes ago \| parent [-]
		By restricted networks, like hospitals, workplaces, schools, etc. If their firewalls can detect it not being typical http/s traffic, they can block it.

▲

minimaltom 7 minutes ago | parent | prev [-]

I'm with you- the attack surface of openssh (and my trust in damien) is a better match imo