From owner-freebsd-arch Mon Jun 26 9:16: 6 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6911A37BF31 for ; Mon, 26 Jun 2000 09:15:59 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA09868; Mon, 26 Jun 2000 10:15:49 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA18734; Mon, 26 Jun 2000 10:15:36 -0600 (MDT) (envelope-from nate) Date: Mon, 26 Jun 2000 10:15:36 -0600 (MDT) Message-Id: <200006261615.KAA18734@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Will Andrews Cc: arch@FreeBSD.ORG Subject: Re: Disabling inetd? In-Reply-To: <20000626053525.U85886@argon.gryphonsoft.com> References: <20000626053525.U85886@argon.gryphonsoft.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was just a few minutes ago talking with some of my colleagues about > disabling inetd completely in a default install. > > What are people's opinions about doing this? I think it's a bad idea, and assumes that the 'default' installation is a box that's running 24/7 connected directly to the internet. I only have one box that is 'vulnerable' to the internet, and it's my firewall. All the other boxes are inside the firewall, and can (and do) run the other daemons since they are most useful, *especially* for configuring the box. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message