From owner-freebsd-ports Sat Oct 7 9:33:22 2000 Delivered-To: freebsd-ports@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 543E037B66C for ; Sat, 7 Oct 2000 09:33:20 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id EF0001C72; Sat, 7 Oct 2000 12:33:06 -0400 (EDT) Date: Sat, 7 Oct 2000 12:33:06 -0400 From: Bill Fumerola To: Mike Meyer Cc: freebsd-ports@FreeBSD.org Subject: Re: ports/21814: Inetd's very existence is a security risk. Message-ID: <20001007123306.L38472@jade.chc-chimes.com> References: <200010071150.EAA21816@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200010071150.EAA21816@freefall.freebsd.org>; from mwm@mired.org on Sat, Oct 07, 2000 at 04:50:02AM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Oct 07, 2000 at 04:50:02AM -0700, Mike Meyer wrote: > Didn't really read the PR carefully, did you? The relevant part is: > > I always (always, always, always) turn off inetd on any system > that needs to be secured against exposure to the world. I'd > really it rather not be on the system *at all*. > > In other words, I *know* how to turn, but I want it gone > completely. The patch makes that much saner. If you don't like that > behavior, don't add NO_INETD to /etc/make.conf. This is getting borderline absurd. If you don't like it don't run it. All the other NO_*'s are typically because the program is one that takes a long time to build(usually with no benefit, see ObjC..), conflicts with other programs that do the same thing (sendmail, lpr), or are illegal for some of us to use. We dnn't just make them because we hate the very existance of a program[1]. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org 1. Well, maybe NOPERL counts... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message