From owner-freebsd-questions@FreeBSD.ORG Fri May 12 20:41:37 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C6EE16AA30 for ; Fri, 12 May 2006 20:41:37 +0000 (UTC) (envelope-from wmc20@xxiii.com) Received: from imf25aec.mail.bellsouth.net (imf25aec.mail.bellsouth.net [205.152.59.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id C26D443D68 for ; Fri, 12 May 2006 20:41:28 +0000 (GMT) (envelope-from wmc20@xxiii.com) Received: from ibm69aec.bellsouth.net ([68.209.177.221]) by imf25aec.mail.bellsouth.net with ESMTP id <20060512204127.PXQB15723.imf25aec.mail.bellsouth.net@ibm69aec.bellsouth.net> for ; Fri, 12 May 2006 16:41:27 -0400 Received: from wcox.bellsouth.net ([68.209.177.221]) by ibm69aec.bellsouth.net with ESMTP id <20060512204127.KZFW21509.ibm69aec.bellsouth.net@wcox.bellsouth.net> for ; Fri, 12 May 2006 16:41:27 -0400 Message-Id: <6.2.3.4.2.20060512163433.02e85298@mailsvr.xxiii.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Fri, 12 May 2006 16:41:36 -0400 To: freeBSD Questions From: wc_fbsd@xxiii.com In-Reply-To: <6.0.0.22.2.20060512152402.026a60c8@mail.computinginnovatio ns.com> References: <4464B95D.1040702@computer.org> <20060512171515.GC34035@catflap.slightlystrange.org> <4464CEDA.80906@computer.org> <6.0.0.22.2.20060512152402.026a60c8@mail.computinginnovations.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: Pros and Cons of running under inetd.... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2006 20:41:37 -0000 At 04:25 PM 5/12/2006, you wrote: >inetd running is discouraged. Instead run the daemons on boot using >rc scripts. If you look back in the history, inetd running is a >security risk, and was discouraged in the 5.X releases. Is that still really true? Waaayyy back when, inetd would have all kinds of dangerous services enabled by default (allowing DOS stuff like spewing "chargen" into "discard"). But that was a configuration issue, and issues with the services it launched; not with inetd itself. The authentication is still done within ftpd. You're just saving the tiny overhead of running it all the time for occasional use. And inetd does allow the tcpwrappers for anything it launches (obviously the wrappers are compiled into many other things now, ftpd included.) -Wayne