Here's a pretty good introductory article on Linux security. It discusses configuring TCPserver as a replacement for inetd, Dan Bernstein and the crypto code that he's contributed to the community, and explanations of the security implications of many of the common network services. "I got bored with articles telling you to edit inetd.conf too. So I'm not going to do it the official way - I'm going to do it my way. I'm an amateur at this, so I don't know how good my way is. It might be wonderful or it might be awful, but at least it's uncommon. The first step is flushing inetd down the drain and replacing it with tcpserver. "
News: Host Security
