From owner-freebsd-ports@FreeBSD.ORG Fri Jun 24 08:01:18 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20A3616A41C for ; Fri, 24 Jun 2005 08:01:18 +0000 (GMT) (envelope-from lupe@lupe-christoph.de) Received: from buexe.b-5.de (buexe.b-5.de [84.19.0.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id A635E43D55 for ; Fri, 24 Jun 2005 08:01:16 +0000 (GMT) (envelope-from lupe@lupe-christoph.de) Received: from buexe.b-5.de (www-data@localhost [127.0.0.1]) by buexe.b-5.de (8.12.3/8.12.3/b-5/buexe-3.4) with ESMTP id j5O80mQU002383; Fri, 24 Jun 2005 10:00:48 +0200 Received: (from www-data@localhost) by buexe.b-5.de (8.12.3/8.12.3/b-5/buexe-msp1.2) id j5O80mZP002381; Fri, 24 Jun 2005 10:00:48 +0200 Received: from blueice3n1.de.ibm.com (blueice3n1.de.ibm.com [195.212.29.179]) by buexe.b-5.de (IMP) with HTTP for ; Fri, 24 Jun 2005 10:00:47 +0200 Message-ID: <1119600047.42bbbdafe55ad@buexe.b-5.de> Date: Fri, 24 Jun 2005 10:00:47 +0200 From: Lupe Christoph To: fbsd_user@a1poweruser.com References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.2 Cc: ports@freebsd.org Subject: RE: FreeBSD Port: doorman-0.8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jun 2005 08:01:18 -0000 Quoting fbsd_user : > > One last thing. Doorman has a ms/windows knock program available > as > > a .zip file. Sure would be nice to have that zip file included > with > > the port alone with a example Windows's script combining the knock > > exec with say FTP or telnet. > This is a FreeBSD port. It does not even include the doorman code. > Why should it include something that is not even needed to run > doorman > on FreeBSD? > REPLY: BACAUSE MANY FREEBSD USERS HAVE LARGE USER COMMUNITIES THAT > USE WINDOWS BOXS TO ACCESS THEIR FREEBSD SERVER THATS WHY. Are you argouing that FreeBSD ports of server software that can provide a Windows client should include that client? Sorry, I can't support that view. When I add something to the port, I feel I must be able to support it. I can't even compile Windows software, let alone debug it. So, no I will not add Windows software to this port. > I wrote the current handbooks firewall section and I think this > doorman port is so important that I am going to add reference to it > in the update I am writing to the firewall section. That is why I > have been testing it and corresponding with you about enhancements > to the install process. I appreciate the additional exposure this port will get through your work. Even more would I appreciate if you were able to test doormand with ipfw. I don't have the time to set up infrastructure to do this test. > Thanks for your fast replies in this matter. You are doing a good > job. Thanks for the flowers ;-) Lupe Christoph -- | lupe@lupe-christoph.de | http://www.lupe-christoph.de/ | | "... putting a mail server on the Internet without filtering is like | | covering yourself with barbecue sauce and breaking into the Charity | | Home for Badgers with Rabies. Michael Lucas |