From owner-freebsd-questions@FreeBSD.ORG Wed Dec 1 18:06:22 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 3C6F516A4CE for ; Wed, 1 Dec 2004 18:06:22 +0000 (GMT) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBA1543D5F for ; Wed, 1 Dec 2004 18:06:21 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from [10.0.0.10] (12-218-40-24.client.mchsi.com[12.218.40.24]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20041201180621m9100ceoose>; Wed, 1 Dec 2004 18:06:21 +0000 From: Josh Paetzel To: "Charles Ulrich" Date: Wed, 1 Dec 2004 12:04:10 +0000 User-Agent: KMail/1.7 References: <43711.24.11.146.21.1101922894.squirrel@24.11.146.21> In-Reply-To: <43711.24.11.146.21.1101922894.squirrel@24.11.146.21> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412011204.10599.josh@tcbug.org> 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:06:22 -0000 On Wednesday 01 December 2004 17:41, you 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. > > Thanks! This may or may not help you, but I generally firewall ssh so that only known addresses can get in. (whitelisting as opposed to blacklisting) -- Thanks, Josh Paetzel