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.
Optional information specified with the daemon@server form:
Optional information specified with the user@client form:
The same request, pretending that hostname lookup failed: tcpdmatch in.telnetd 127.0.0.1
To predict what tcpd would do when the client name does not match the client address: tcpdmatch in.telnetd paranoid
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:
tcpdchk(8), tcpd configuration checker hosts_access(5), format of the tcpd access control tables. hosts_options(5), format of the language extensions. inetd.conf(5), format of the inetd control file. tlid.conf(5), format of the tlid control file.AUTHORSWietse Venema (wietse@wzv.win.tue.nl), Department of Mathematics and Computing Science, Eindhoven University of Technology Den Dolech 2, P.O. Box 513, 5600 MB Eindhoven, The Netherlands \" @(#) tcpdmatch.8 1.5 96/02/11 17:01:35