A common question I get from individuals who use Internet-accessible SSH to manage their network devices concerns how do deal with all the unwanted Bruteforcing activity that is usually attracted. While changing the default SSH listening port number and/or implementing a Source-IP based Access Control List would seem like common sense solutions, there are still situations where it is either not possible to move the SSH listening port or not practical to implement an Access Control List if the application involves providing access from dynamic Internet address space. I recently became aware of an interesting initiative at http://www.sshbl.org where a collection of SSH Bruteforcing attempts by source IP ...