I didn't think I'd evoke such a response. Here goes... I'm happy with my inetd service and tcpserver for my qmail-smtp. I'm running a few low-load services through inetd and it's doing fine. Perhaps if pop3 or imap become a larger load when I deploy web based email, I'll run them with tcpserver too. I was just mainly trying to point out the hole in the You-Must-Use-Tcpserver-Because-Inetd-Is-A-DoS-Risk argument - that you can simply attack a different service. - David Harris Principal Engineer, DRH Internet Services
- Re: Is inetd really unreliable? Bruce Guenter
- Re: Is inetd really unreliable? Markus Stumpf
- Re: Is inetd really unreliable? Johannes Erdfelt
- Re: Is inetd really unreliable? Bruce Guenter
- Re: Is inetd really unreliable? Johannes Erdfelt
- Re: Is inetd really unreliable? Markus Stumpf
- RE: Is inetd really unreliable? David Harris
- Re: Is inetd really unreliable? Racer X
- Re: Is inetd really unreliable? Johannes Erdfelt
- Re: Is inetd really unreliable? Adam D . McKenna
- Re: Is inetd really unreliable? David Harris
- Re: Is inetd really unreliable? Mirko Zeibig
- Re: Is inetd really unreliable? Bruce Guenter
- Re: Is inetd really unreliable? James J. Lippard
