Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Incidents
[Top] [All Lists]

Re: Distributed Bruteforce against SSH

Subject: Re: Distributed Bruteforce against SSH
Date: Mon, 12 May 2008 15:53:56 -0400
On Mon, May 12, 2008 at 2:01 PM, Keith T. Morgan
<keith.morgan@terradon.com> wrote:
I wanted to follow up on this after putting a little more thought into it.  
Honestly, I'm quite impressed by the intelligence the botnet is exhibiting.  
Based on the testing I've done, it's clear that the entire botnet is 
collectively sharing its position in the dictionary on a per-target basis.  
Fairly slick, IMO.

Agreed.

If you're concerned, start requiring ssh-keys for authentication.  If
you use RedHat (or derivatives thereof) and have the pam_succeed_if
PAM module available, you can at the very least make sure that any
non-authorized user accounts (even if they actually exist, and have a
password) can't log in via ssh.    Like users who only get email
privileges, or who only have ftp privs to update a website.

Mitigation is the name of the game, since the botnets tend to span
large areas of the IP space, blocking entire networks risks making
your servers/services unusable.

-Tim

<Prev in Thread] Current Thread [Next in Thread>