fail2bban with knockd & whitelist
fail2bban with knockd & whitelist
Posted May 15, 2008 0:04 UTC (Thu) by AnswerGuy (guest, #1256)In reply to: Brute-Force SSH Server Attacks Surge (InformationWeek) by endecotp
Parent article: Brute-Force SSH Server Attacks Surge (InformationWeek)
I use fail2ban with a whitelist on port 22 and port knocking on two additional ports (with a five port knock for each). Thus I can be assured that I can still get in even if someone has spoofed failures from some adress I'm using that's not on my whitelist. I could just turn off port 22 on that server since I only ever use one of the alternatives. The advantage of fail2ban or its ilk in this case is to prevent the bandwidth and CPU hit for repeated brute force ssh attempts. hiding the alternatives behind a knock sequence is even more effective since the casual port scanners can't even find the running service. If I see brutish failures on one of the alternative ports then I can be certain that someone sniffed my knock sequnce ... and change it.
