TCP wrappers - starting tcpd ?
Kristian Rink
kristian at zimmer428.net
Fri Aug 25 11:27:08 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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...
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)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE7t6ScxBAPOA1m6wRAr0FAJ98VGUp/A3bhVOa6A1GD6F1ROzlBACfbezO
551h2EmzUaY2YfBk20vYJJM=
=lujU
-----END PGP SIGNATURE-----
More information about the ubuntu-users
mailing list