Whole document tree 17.5. tcp_wrappertcp_wrapper is a library which can help you to protect service against misuse. 17.5.1. Filtering capabilitiesYou can use tcp_wrapper for
17.5.2. Which program uses tcp_wrapperFollowing are known:
17.5.3. Usagetcp_wrapper is controlled by two files name /etc/hosts.allow and /etc/hosts.deny. For more information see
17.5.3.1. Example for /etc/hosts.allowIn this file, each service which should be positive filtered (means connects are accepted) need a line.
17.5.3.2. Example for /etc/hosts.denyThis file contains all negative filter entries and should normally deny the rest using
If this node is a more sensible one you can replace the standard line above with this one, but this can cause a DoS attack (load of mailer and spool directory), if too many connects were made in short time. Perhaps a logwatch is better for such issues.
17.5.4. LoggingDepending on the entry in the syslog daemon configuration file /etc/syslog.conf the tcp_wrapper logs normally into /var/log/secure. 17.5.4.1. Refused connectionA refused connection via IPv4 to an xinetd covered daytime service produces a line like following example
A refused connection via IPv4 to an dual-listen sshd produces a line like following example
17.5.4.2. Permitted connectionA permitted connection via IPv4 to an xinetd covered daytime service produces a line like following example
A permitted connection via IPv4 to an dual-listen sshd produces a line like following example
|