Full Disclosure mailing list archives

Re: SSH brute force blocking tool


From: "Brian Eaton" <eaton.lists () gmail com>
Date: Tue, 28 Nov 2006 12:33:53 -0500

(Resending since this somehow didn't make it to the list the first
time.  Apologies if you receive two copies.)

On 11/28/06, Thierry Zoller <Thierry () zoller lu> wrote:
Dear Tavis,

TO> J, you have made an attempt to fix it, but is is not sufficient.
TO> An attacker can still add arbitrary hosts to the deny list.

Can you propose a fix ? Apart from the aggressivness of this thread
I find it interesting to read (from a tech standpoint).

Unlike Tavis, I haven't had the guts to actually install and test this
little contraption.  But it looks like setting the sshd config option
"UseDNS no" might help.  Then sshd will log the client IP instead of
the client hostname, and you no longer need to rely on the attacker's
DNS to tell you which IP to blacklist.

Someone could still purposefully trigger a ban of an IP address they
controlled, but I don't think they could do arbitrary IPs any longer.

Regards,
Brian

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


Current thread: