full-disclosure - Re: Distributed SSH username/password brute forceattack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <471D1E56.5080102@kallisti.se>
Date: Tue, 23 Oct 2007 00:04:06 +0200
From: Anders B Jansson <hdw@...listi.se>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: Distributed SSH
	username/password	brute	forceattack

A.L.M.Buxey@...ro.ac.uk wrote:
> Hi,
> 
>> Oct 22 20:36:13 nms sshd[90657]: Failed password for invalid user gopher 
>> from 77.46.152.2 port 55120 ssh2
> 
> user/password authentication for SSH?  one way of cleaning up your
> logs and killing this type of attack is to reconfigure your OpenSSH
> to only allow key based logins. stopped my 10M+ logfiles straight away

An even better way is to punt the attackers to a 'silent drop' table in your firewall.

Cuts your logs to nothing and keeps the kiddies wasting their time.

The latest attack surge is either directed or a bit more clever, haven't seen anything on my random user DSL traps.
-- 
// hdw

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