Date: 24 Dec 1998 11:08:16 -0500 From: Chris Shenton <cshenton@uucom.com> To: Barrett Richardson <brich@aye.net> Cc: freebsd-security@FreeBSD.ORG Subject: Re: Do I really need inetd? Message-ID: <86ww3hh6a7.fsf@samizdat.uucom.com> In-Reply-To: Barrett Richardson's message of Thu, 24 Dec 1998 00:13:09 -0500 (EST) References: <Pine.BSF.3.96.981224000443.29305A-100000@phoenix.aye.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Barrett Richardson <brich@aye.net> writes: > I have all my necessary network services running as daemons. In the > face of recent discoveries of problems caused for inetd by nmap > and various things I've come to the conclusion that I really don't > need inetd -- another variable I can eliminated from the mix. > > Any undesirable side effects come to mind? When I set up a new box, I usually first install sshd. Then I find I can usually turn off inetd because I don't need any services there: telnet and ftp can be replaced with ssh/scp, other services (finger, chargen) are of little or no use and pose unnecessary risks. This is typically for production servers; your tolerance for risk on desktop or home boxes will dictate how fascist you want to be. Having said that, if I do want something different (e.g., amanda, rstatd), I'll run inetd but with only these lines in the inetd.conf file, and I'll tcp_wrap them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ww3hh6a7.fsf>