From owner-freebsd-questions Wed Jul 26 16:57:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id F38B037B8C4 for ; Wed, 26 Jul 2000 16:57:37 -0700 (PDT) (envelope-from williamsl@home.com) Received: from RELIABLE ([24.4.115.31]) by mail.rdc1.tn.home.com (InterMail vM.4.01.02.00 201-229-116) with ESMTP id <20000726235736.DOEF25440.mail.rdc1.tn.home.com@RELIABLE> for ; Wed, 26 Jul 2000 16:57:36 -0700 Date: Wed, 26 Jul 2000 19:57:39 -0400 From: Ben Williams X-Mailer: The Bat! (v1.45) Personal Organization: Williams Enterprises X-Priority: 3 (Normal) Message-ID: <7448379743.20000726195739@home.com> To: freebsd-questions@FreeBSD.ORG Subject: portsentry Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Along firewalling lines, does anyone use portsentry? It's available in ports and I have it installed on a non-critical machine and it has already blocked a few IP's for trying to connect to ports I don't offer services on. Any comments on the reliability of or wisdom in using portsentry? --Ben Williams mailto:received@email dot com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message