From owner-freebsd-questions@FreeBSD.ORG Tue Jan 25 09:24:44 2005 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 2592F16A4CE for ; Tue, 25 Jan 2005 09:24:44 +0000 (GMT) Received: from smtp1.wanadoo.fr (smtp1.wanadoo.fr [193.252.22.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id D02BC43D41 for ; Tue, 25 Jan 2005 09:24:43 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (mail.bara.nl [127.0.0.1]) by mwinf0104.wanadoo.fr (SMTP Server) with ESMTP id A7D271FFFF68 for ; Tue, 25 Jan 2005 10:24:42 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf0104.wanadoo.fr (SMTP Server) with ESMTP id 8A01E1FFFFCF for ; Tue, 25 Jan 2005 10:24:42 +0100 (CET) X-ME-UUID: 20050125092442565.8A01E1FFFFCF@mwinf0104.wanadoo.fr Date: Tue, 25 Jan 2005 10:24:42 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <134496582.20050125102442@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <41F60ECC.8050206@myunix.net> References: <41F60ECC.8050206@myunix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Banning ips for some time? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 09:24:44 -0000 Christian Tischler writes: CT> Hi, CT> as I have an DSL line witch is 24/7 online (coming from an big and CT> popular provider) my servers sshd reports 30 to 50 failed CT> root/operator/etc. logins a day. I would like to block the incoming ip CT> for a few days automaticly after e.g failed login requests. CT> Currently I am using ipf, but it would be no problem to use any other CT> FreeBSD firewall. CT> This is not only for security reasons, but also to shorten the daily CT> security run output :-) Do you have a need to access your server from the outside Net? If not, you can just block the SSH port entirely at the firewall (which is what I do). Almost doesn't count in securityland, so as long as the logins are failing, they're not a security risk, just a nuisance. -- Anthony