host.allow strictly by xinetd?

dman777 · 01-07-2011, 11:57 AM

Are the TCP wrappers host.allow and host.deny strictly done through xinetd?

trickykid · 01-07-2011, 01:06 PM

TCP Wrappers is a daemon that is run instead of inetd. It intercepts requests and either allows inetd to run and service the request or does not run inetd, thereby denying the request.
TCP Wrappers handles telnet, finger, ftp, exec, rsh, rlogin, tftp, talk, comsat, and other services that have a one-to-one mapping onto executable files.

dman777 · 01-08-2011, 08:44 PM

In my book "Red Hat Certified Technician & Engineer" it states "TCP Wrappers is a host-based service taht allows you to control access into a system from remote hosts sending serviec requests via xinetd daemon".

I thought TCP wrappers could be used with xinetd, but could also be independent of xinetd. Which one would it be?

chrism01 · 01-11-2011, 05:36 PM

Read & digest http://itso.iu.edu/TCP_Wrappers

In short, TCP Wrappers is a library used by xinetd and optionally other servers/services if compiled to include it.

You can check by using

Code:

ldd $(which <servicename>)|grep libwrap

# or

strings $(which <servicename>)|grep hosts