Date: Fri, 12 May 2006 16:41:36 -0400 From: wc_fbsd@xxiii.com To: freeBSD Questions <questions@freebsd.org> Subject: Re: Pros and Cons of running under inetd.... Message-ID: <6.2.3.4.2.20060512163433.02e85298@mailsvr.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.3.4.2.20060512163433.02e85298>