3 ms·
I kind of like running SSH on the default port as it gives me a list of IPs to firewall against on other web facing services across my infrastructure. If someo
by laumars 13y ago
I kind of like running SSH on the default port as it gives me a list of IPs to firewall against on other web facing services across my infrastructure.
If someone is trying to break into my server(s) via SSH, then I sure as hell don't want them to have access to any other services regardless of how secure they might be.
- tlrobinson 13y agoCouldn't you just have your firewall log attempted connections to 22, regardless of whether or not you have SSH running on it?
- noir_lord 13y agoI've also seen people run a fake SSH server on 22 and log attempts (if you know that you don't use 22 then any connection attempt on 22 is interesting).
- laumars 13y ago"Just"? That requires more work to set up than my method and offers no additional security benefits as you're still running an open SSH port. You're falling into the common trap of security through obscurity. But in fact it's very easy to find which port SSH listening on even when you're using a non-standard on. However if you harden SSH properly then it doesnt matter what port it's listening on. So your method is more work for zero gain