3 ms·
> capture your passwords With public key auth, an attacker can't capture anything useful (unless of course they record traffic and later figure out a way to la
by csense 13y ago
> capture your passwords
With public key auth, an attacker can't capture anything useful (unless of course they record traffic and later figure out a way to later capture the private key [1], but this isn't a problem that changing the port will fix).
> mimics SSH
You can't mimic the key files in /etc/ssh/ssh_host_whatever_key without root privileges, assuming these files are properly secured. So users will get an unexpected warning that the host key has changed.
> simple script that listens to port 2222
True -- in cases where something isn't already listening on 2222. But if sshd is started early in the boot process and listens on 2222, won't any script started as a regular user be unable to bind to the socket?
[1] https://news.ycombinator.com/item?id=6609601 https://news.ycombinator.com/item?id=6609601
- edvinbesic 13y agoAlso, what if ssh is on port 1023, which is still a non standard port, not default but privileged, does this help in any way? I'm asking because I don't really know but have to set up my own servers from time to time (hobby admin). Edit: I always use key based auth, don't allow root etc.
- rhubarbquid 13y agoI can't say for sure it would help in any useful way, but it won't reduce your security to run ssh on port 1023.
- glesica 13y agoIt cleans up your log files, that's why I do it. If you run ssh on port 22 your log files with be full of script kiddies with turnkey exploits spamming every IP address they can find. Change the port and suddenly that the logs get much, much quieter. So it's not really a security technique, it's a convenience technique.