News for hackers. Stuff that matters.
Re:Why Putting SSH On Another Port is a Good Idea by relix on Saturday October 26, 2013 @05:48AM (#6616859)
No it isn't. Every server runs SSH, so this is more like there's a field, and you know there's a tank in the field, but you can't see it.

The next thing you do then is take out your standard radar device which scans the field, and pinpoints exactly where the tank is in 3 seconds, and then you aim your tank buster at that spot and fire.

Re:Why Putting SSH On Another Port is a Good Idea by maaku on Saturday October 26, 2013 @07:21PM (#6619868)
Or, you put up a fake, camouflaged tank and let the enemy reveal themselves when they attack it. (Leave 22/tcp open as a honeypot, triggering an immediate iptables drop).
Re:Why Putting SSH On Another Port is a Good Idea by serans on Saturday October 26, 2013 @07:41AM (#6617070)
In my experience most of the time "attackers"/script-kiddies just scan over a range of IPs for port 22, and if it's not open on your computer, they just move on to the next IP. That's why you get thousands of requests for port 22 and very few on say port 21.

Of course, not that it would stop someone willing to spend more than a few seconds on attacking your server, but still makes the camo analogy a quite nice one in my opinion.

Re:Why Putting SSH On Another Port is a Good Idea by markeganfuller on Saturday October 26, 2013 @07:21AM (#6617038)
Except unless your only target is that one tank you're not going to scan all its ports.