From owner-freebsd-questions@FreeBSD.ORG Wed Dec 1 18:08:46 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEF3716A4CE for ; Wed, 1 Dec 2004 18:08:46 +0000 (GMT) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD44143D2F for ; Wed, 1 Dec 2004 18:08:46 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.90] ([4.28.157.47]) (authenticated bits=0) by zoot.lafn.org (8.12.3p3/8.12.3) with ESMTP id iB1I8iCV031092 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 1 Dec 2004 10:08:45 -0800 (PST) (envelope-from bc979@lafn.org) In-Reply-To: <43711.24.11.146.21.1101922894.squirrel@24.11.146.21> References: <43711.24.11.146.21.1101922894.squirrel@24.11.146.21> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <09C48337-43C4-11D9-8D0D-000393681B06@lafn.org> Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Wed, 1 Dec 2004 10:08:44 -0800 To: "Charles Ulrich" X-Mailer: Apple Mail (2.619) X-Virus-Scanned: ClamAV 0.80rc4/612/Tue Nov 30 12:26:50 2004 clamav-milter version 0.80j on zoot.lafn.org X-Virus-Status: Clean cc: questions@freebsd.org Subject: Re: blacklisting failed ssh attempts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 18:08:47 -0000 On Dec 1, 2004, at 09:41, Charles Ulrich wrote: > > This morning I noticed that an attacker spent over a full hour trying > to > brute-force accounts and passwords via ssh on one of our machines. > These kinds > of attacks are becoming more frequent. > > I was wondering: does anyone know of a way to blacklist a certain IP > (ideally, > just for a certain time period) after a certain number of failed login > attempts via ssh? I could change the port that sshd listens on, but > I'd rather > find a better solution, one that isn't just another layer of obscurity. I tried null routing their addresses and that stops that address. However, a day or so later they are back from a different address. After a couple months of this I changed the ports. Its a real pain.