Re: tcp wrappers not enabled by default...?

[Christian <christian@global.net.au>]

Theo de Raadt wrote:
> One could argue that our inetd should do tcpwrapper stuff easier, but there's
> gremlins down that path (including MASSIVE complexity increases in inetd)

I'm not necessarily disagreeing with you but what are the problems with
running tcpwrappers out of inetd in its current state?  Speaking
strictly from a user perspective, the only problem I'd noticed with
tcpwrappers was that, if the program didn't run out of inetd (wrapped
with tcpd) and wasn't linked against libwrap then the hosts.allow/deny
would of course have no effect.

Regards,

Christian.