From owner-freebsd-security@FreeBSD.ORG Sat Sep 18 14:29:56 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2259D16A4CE for ; Sat, 18 Sep 2004 14:29:56 +0000 (GMT) Received: from web51007.mail.yahoo.com (web51007.mail.yahoo.com [206.190.38.138]) by mx1.FreeBSD.org (Postfix) with SMTP id B69F943D41 for ; Sat, 18 Sep 2004 14:29:55 +0000 (GMT) (envelope-from chrisryanemail@yahoo.com.au) Message-ID: <20040918142955.61586.qmail@web51007.mail.yahoo.com> Received: from [211.30.19.233] by web51007.mail.yahoo.com via HTTP; Sun, 19 Sep 2004 00:29:55 EST Date: Sun, 19 Sep 2004 00:29:55 +1000 (EST) From: Chris Ryan To: Frankye - ML , freebsd-security@freebsd.org In-Reply-To: <20040918161431.53a63dd3@godzilla> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Attacks on ssh port X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Sep 2004 14:29:56 -0000 > > I've just moved the public port of the sshd on > another port, quite lame > but at least I'm not bothered by worms :) i believe this has to be one of the simplest ways of stopping incoming ssh attacks. If ssh is the only open port and attackers port scan protection - with the appropriate active firewall that blocks their IP address after x failed attempts permanently.... Chris Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com