"HOFMEISTER,JAMES (HP-USA,ex1)" wrote:
> An added concern is with INETD at a 'system process' priority and with
> the child process's being created at these same levels is that INETD is
> a standard (I have a definition of this I will give you later) and that
> increases the likely hood that an external or internal hacker who has
> the ability to launch INETD service request on your system will more
> likely be successful at launching a loss of service attack which in this
> case will not only take out the service, but may also hang our system.

What he said.

It would be easy for a hacker to bring your system to its knees by writing a
program that did a tight loop connecting and disconnecting to the various
services in /etc/inetd.conf (assuming your firewall didn't block these attempts
in the first place).

- Mark B.