3 ms·
Yeah, just moving your SSH daemon from port 22 to some other port number alone can help with that.
by daveidol 6y ago
Yeah, just moving your SSH daemon from port 22 to some other port number alone can help with that.
- foxylad 6y agoWe have continuous distributed dictionary attacks on our SSH servers, with attempts from literally thousands of IP addresses at a cadence designed not to trigger rate alerts. We moved from port 22, and within days all ports were scanned and the attacks started again on the new port. We are working on a different scheme to thwart the attackers.
- civil_engineer 6y agoPort knocking, huh?
- httpsterio 6y agoI faced a similar issue with tens of thousands of login attempts from dozens of unique IP's daily on my server. Moving from 22 helped with some of the traffic but not all. Port knocking however did stop anyone from ever even reaching the right combination and had no login attempts since.
- programmarchy 6y agoYou could generate a random sequence to determine which port to open on any given day.