From owner-freebsd-bugs Fri Dec 28 5:30:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1165637B41A; Fri, 28 Dec 2001 05:30:11 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id fBSDLQa50277; Fri, 28 Dec 2001 05:21:26 -0800 (PST) (envelope-from dwmalone) Date: Fri, 28 Dec 2001 05:21:26 -0800 (PST) From: Message-Id: <200112281321.fBSDLQa50277@freefall.freebsd.org> To: dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org, dwmalone@FreeBSD.org Subject: Re: misc/33261: FreeBSD base system does not install tcpd Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: FreeBSD base system does not install tcpd Responsible-Changed-From-To: freebsd-bugs->dwmalone Responsible-Changed-By: dwmalone Responsible-Changed-When: Fri Dec 28 05:21:03 PST 2001 Responsible-Changed-Why: As you know, tcpd is not installed in the base system because its functionality is built into inetd. If you want to run some services wrapped and some unwrapped then it is simple to do this by adding apropriate allow rules (at the top of) hosts.allow. Alternatively, you can run a second copy of inetd without wrapping. If you want to install something from ports with which you want to use tcpd then you can build tcpd from ports for from the main source tree. It might be useful to have some infrasturcture to do this, but I believe most users who have enough knowlege to decide they want to use tcpd with tcpserver are capable of building tcpd in one of the ways I have mentioned. (Besides, wouldn't using tcpd with tcpserver be some sort of religious travisty ;-) As you point out in -stable, tcpd is a very small program and it wouldn't take up much space we shipped it with the base system. My main fear would be that it would cause more confusion about how tcp wrapping works. People would accidently use both tcpd's and inetd's wrapping and get unexpected effects. We could get around this by adding "tcpd: ALL: allow" to the top of the default hosts.allow, but this is likely to cause even move confusion about hosts.allow. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33261 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message