Re:Why Putting SSH On Another Port is a Good Idea
by gnur on Saturday October 26, 2013 @04:21AM
(#6616760)
What can go wrong by changing the listening port of sshd?
I have changed the port on my vps purely for less clutter in my logs, but I haven't had anything go wrong because of it.
Re:Why Putting SSH On Another Port is a Good Idea
by Nick_C on Sunday October 27, 2013 @01:00AM
(#6620844)
When you have to use the java applet of the Control Panel in your browser to manage your VPS. If your sshd is not on port 22, typically the applet won't find it and you're screwed.
Re:Why Putting SSH On Another Port is a Good Idea
by lttlrck on Saturday October 26, 2013 @12:55PM
(#6618066)
It introduces a communications problem. Which machines are running SSH on a non-standard port and what is it? Plus some tools are harder to set up, IIRC SVN+SSH is one of them.
Re:Why Putting SSH On Another Port is a Good Idea
by GalacticDomin8r on Sunday October 27, 2013 @10:15PM
(#6624696)
> What can go wrong by changing the listening port of sshd?
Read the article.
ephemeral port range are a tunable at least on FreeBSD. However tuning stuff like this is fraught with disaster consider how difficult it is to guess an ssh password vs all things that can go wrong when changing sshd's listening port. But do it if you want, I bill by the hour.
galacticdominator% sysctl net.inet.ip.portrange net.inet.ip.portrange.randomtime: 45 net.inet.ip.portrange.randomcps: 10 net.inet.ip.portrange.randomized: 1 net.inet.ip.portrange.reservedlow: 0 net.inet.ip.portrange.reservedhigh: 1023 net.inet.ip.portrange.hilast: 65535 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.last: 65535 net.inet.ip.portrange.first: 10000 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.lowfirst: 1023