TCPDMATCH(8) | TCPDMATCH(8) |
tcpdmatch predicts how the tcp wrapper would handle a specific request for service. Examples are given below.
The program examines the tcpd access control tables (default /etc/hosts.allow and /etc/hosts.deny) and prints its conclusion. For maximal accuracy, it extracts additional information from your inetd or tlid network configuration file.
When tcpdmatch finds a match in the access control tables, it identifies the matched rule. In addition, it displays the optional shell commands or options in a pretty-printed format; this makes it easier for you to spot any discrepancies between what you want and what the program understands.
daemon | A daemon process name. Typically, the last component of a daemon executable pathname. |
client |
A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns. |
Optional information specified with the daemon@server form:
server | A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns. The default server name is `unknown'. |
Optional information specified with the user@client form:
user | A client user identifier. Typically, a login name or a numeric userid. The default user name is `unknown'. |
-d | Examine hosts.allow and hosts.deny files in the current directory instead of the default ones. |
-i inet_conf | Specify this option when tcpdmatch is unable to find your inetd.conf or tlid.conf network configuration file, or when you suspect that the program uses the wrong one. |
The same request, pretending that hostname lookup failed:
To predict what tcpd would do when the client name does not match the client address:
On some systems, daemon names have no `in.' prefix, or tcpdmatch may need some help to locate the inetd configuration file.
The default locations of the tcpd access control tables are:
/etc/hosts.allow
August 25, 2011 |