Re:Ask HN: Anonymous person sent proof of SSH access to our ...
by MichaelGG on Wednesday July 27, 2016 @03:13PM
(#12175704)
How is port knocking not, I dunno, at least 10x more inconvenient for users?
FWIW, I've never seen a brute force attack on SSH other than on port 22. Most likely, a targeted attacker would realise if you change the port, you're probably not going to have a trivial password.
Re:Ask HN: Anonymous person sent proof of SSH access to our ...
by more_corn on Wednesday July 27, 2016 @04:43PM
(#12176371)
I agree, I set up port knocking and it's a huge pain in the butt (so much so that I never moved it out of testing). It also lacks cryptographic verification. It's a lot of trouble for a not quite ideal solution.
Re:Ask HN: Anonymous person sent proof of SSH access to our ...
by aaronmdjones on Wednesday July 27, 2016 @09:04PM
(#12177697)
The Single Packet Authorization variant of port knocking has built-in authentication.
Re:Ask HN: Anonymous person sent proof of SSH access to our ...
by laumars on Wednesday July 27, 2016 @04:44PM
(#12176378)
Port knocking is more inconvenient but its also more secure. I'm not advocating it though, just example how low down the scale I consider non-standard ports as a sensible recommendation.
Random IPs are unlikely to be port scanned but any reasonably popular site will.
If you really want to hide SSH from script kiddies then you're better off setting up firewall rules to whitelist trusted IPs. Heck, even port knocking[1] would be a better option than changing the port number.
[1] https://en.wikipedia.org/wiki/Port_knocking