Nils Breunese wrote:
+1 on that. I've used both of those tools, and they both work. I don't use custom ports anymore, either, for this reason. My preference is now for Fail2Ban, because I prefer IPTables-style blocking. But that's just me.Nadav Kavalerchik wrote:just a little advise for the time you get it fixed we had alloooooot of log warnings of hackers trying to crack the machine through port 22 so we moved it very high... beyond 62744 now all is quiet :-)I like to set up public key authentication and then disable password authentication for SSH. Then install a brute-force blocker like DenyHosts  or Fail2Ban  and things are also quiet. And our users don't need to specify a custom port.Nils Breunese.