From owner-freebsd-questions@FreeBSD.ORG Fri Oct 15 08:24:27 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 41E8816A4CE for ; Fri, 15 Oct 2004 08:24:27 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDF3743D1F for ; Fri, 15 Oct 2004 08:24:26 +0000 (GMT) (envelope-from holle@ackw.de) Received: from [212.227.126.205] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CINNy-0007q8-00 for freebsd-questions@freebsd.org; Fri, 15 Oct 2004 10:24:26 +0200 Received: from [194.231.186.52] (helo=laptop.richard) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CINNx-0006MO-00 for freebsd-questions@freebsd.org; Fri, 15 Oct 2004 10:24:26 +0200 From: Richard Verwayen To: freebsd-questions@freebsd.org In-Reply-To: <20041014210906.761aa524@vixen42.24-119-122-191.cpe.cableone.net> References: <200410131404.i9DE4ONU047345@bmcgover-pc.cisco.com> <4ACDF26414DB010421A6AD6C@utd49554.utdallas.edu> <20041014210906.761aa524@vixen42.24-119-122-191.cpe.cableone.net> Content-Type: text/plain Message-Id: <1097828663.9165.23.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 15 Oct 2004 10:24:23 +0200 Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:6ba71b1a14e66764b295fb16b9247c3e Subject: Re: Automatic Firewall software? 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: Fri, 15 Oct 2004 08:24:27 -0000 On Fri, 2004-10-15 at 04:09, Vulpes Velox wrote: > > Doesn't Portsentry ignore ports that have a service bound to them > > like the SSH daemon? In that case, it wouldn't help Brian's problem, > > since ssh is running, portsentry would ignore any attacks to port > > 22, right? > > Move it and the like to a non-common port if one can. :) Security by obscurity??? ======================== NO! There is a tiny little configuration file to change portsentries behaviour! So tell portsentry not to listen on used ports! Richard