Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
1–10 of 200 posts
Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#2Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#3Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#4That’s a super cool concept, but doesn’t this fall a bit under “security by obscurity”?
Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#5That’s a super cool concept, but doesn’t this fall a bit under “security by obscurity”?
Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#6Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#7That’s a super cool concept, but doesn’t this fall a bit under “security by obscurity”?
Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#8That’s a super cool concept, but doesn’t this fall a bit under “security by obscurity”?
Re: Tosh: Changing your SSH server's listen address every 30 seconds based on TOTP
#9That’s a super cool concept, but doesn’t this fall a bit under “security by obscurity”?
Yes, but that's only bad if it's your only security.
The number one step any public‐facing SSH server should take is to switch from password auth to keys only. Anyone who’s still concerned can put it behind a WireGuard VPN. Layers typically added beyond that (like changing port, etc.) don’t even register on the security scale, so to speak.
The tweet that inspired the post mentioned port knocking which has always been rather ridiculous given those alternatives.