Re:Why Putting SSH On Another Port is a Good Idea
by MarkMc on Saturday October 26, 2013 @09:48AM
(#6617369)
Firstly, I like the tone you used to concede your original point.
As to whether the port should be below 1024 or above 60000, I am undecided. I'd love to see some empirical data on this: let's say I run ssh over several days on port 22, port 762 and port 90332. How many connections do I get for each port?
Re:Why Putting SSH On Another Port is a Good Idea
by jstanley on Saturday October 26, 2013 @04:24PM
(#6619152)
For 90332, I suspect not many :)
Re:Why Putting SSH On Another Port is a Good Idea
by Quai on Sunday October 27, 2013 @06:55AM
(#6621544)
Highest port number is limited by the port field in TCP[1]; a unsigned short (2^16, 0-65535).
http://en.wikipedia.org/wiki/Transmission_Control_Protocol#T...
I'd say it differently, though. Instead of defending the original point, which was bad, I'd instead say among all other controls--most important of which is patching, removing passwords, etc.--one control is running below 1024.
I could go for that.
Except I actually think the gain from being up high (over 60K) is greater than the gain from being below 1024. It's not about being invincible, it's about not being a target at all.