TCP wrappers - starting tcpd ?

[Dave S]

On Friday 25 August 2006 12:27, Kristian Rink wrote:
> Am Fri, 25 Aug 2006 12:21:03 +0100
>
> schrieb Dave S <ubuntu at pusspaws.net>:
> > I would have expected tcpd to be running scouring /etc/hosts.????
> > periodically since changes in /etc/hosts.???? are supposed to be
> > actioned immediately.
>
> [...]
>
> > So no tcpd ... checking /etc/init.d I cant find anything that may
> > start tcpd - assuming that is that tcpd should be running (only my
> > guess :)
>
> Not sure about the ssh thing, but for what I know, tcpd is supposed to
> be started by inetd in response to any connection attempted to a
> port/service managed by inetd. inetd then will pass the connection
> request to tcpd which checks (using the hosts.* files) whether to
> allow/deny connection and invoke the "right" service or drop the
> connection request instead.
>
> Thus, you shouldn't have a starter script for tcpd in init.d, nor
> should there be any tcpd processes running. You could check this out
> using a service like, say, ftp exposed using inetd...

Ah I was hopeing that I did not have to use inetd - due to security concerns 
but what you say makes sense.

Dave


>
> HTH, best regards...
> Kristian
>
> --
> Kristian Rink *  http://zimmer428.net * jab: kawazu at jabber.ccc.de
> icq: 48874445 *  fon: ++49 176 2447 2771
> "One dreaming alone, it will be only a dream; many dreaming together
> is the beginning of a new reality." (Hundertwasser)