From owner-freebsd-questions@FreeBSD.ORG Sun Aug 8 05:21:19 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 0499516A4CE for ; Sun, 8 Aug 2004 05:21:19 +0000 (GMT) Received: from grog.secure-computing.net (grog.secure-computing.net [63.228.14.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7825843D1F for ; Sun, 8 Aug 2004 05:21:18 +0000 (GMT) (envelope-from ecrist@secure-computing.net) Received: from Nomad (nat-server.secure-computing.net [63.228.14.245]) (authenticated bits=0)i785LGNo000803; Sun, 8 Aug 2004 00:21:16 -0500 (CDT) (envelope-from ecrist@secure-computing.net) From: "Eric Crist" To: "'Mike Bruce'" , Date: Sun, 8 Aug 2004 00:17:28 -0500 Message-ID: <000701c47d07$01e674e0$6401a8c0@Nomad> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Virus-Scanned: clamd / ClamAV version 0.74, clamav-milter version 0.74a on grog.secure-computing.net X-Virus-Status: Clean Subject: RE: Hacker Scans - Advice requested 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: Sun, 08 Aug 2004 05:21:19 -0000 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Mike Bruce > Sent: Sunday, August 08, 2004 12:16 AM > To: questions@freebsd.org > Subject: Hacker Scans - Advice requested > > > Please can you help me? > > I am getting increasingly plagued by this message in my > security log on my V4 installations of FreeBSD > > 06:48:53 mail sshd[18617]: Failed password for illegal user > admin from 210.3.4.71 port 39741 ssh2 Aug 7 > > Is there any way that this can be prevented without impairing > the services provided by the operating system. > > Many thanks > > Mike Bruce Very simple solution: create a rule to allow only traffic from known subnets. This will completely deny requests from IP addresses you're not sure of. HTH Eric F Crist