source: trunk/third/tcp_wrappers/tcpdmatch.8 @ 11717

Revision 11717, 3.2 KB checked in by danw, 26 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r11716, which included commits to RCS files with non-trunk default branches.
Line 
1.TH TCPDMATCH 8
2.SH NAME
3tcpdmatch \- tcp wrapper oracle
4.SH SYNOPSYS
5tcpdmatch [-d] [-i inet_conf] daemon client
6.sp
7tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client
8.SH DESCRIPTION
9.PP
10\fItcpdmatch\fR predicts how the tcp wrapper would handle a specific
11request for service.  Examples are given below.
12.PP
13The program examines the \fItcpd\fR access control tables (default
14\fI/etc/hosts.allow\fR and \fI/etc/hosts.deny\fR) and prints its
15conclusion.  For maximal accuracy, it extracts additional information
16from your \fIinetd\fR or \fItlid\fR network configuration file.
17.PP
18When \fItcpdmatch\fR finds a match in the access control tables, it
19identifies the matched rule. In addition, it displays the optional
20shell commands or options in a pretty-printed format; this makes it
21easier for you to spot any discrepancies between what you want and what
22the program understands.
23.SH ARGUMENTS
24The following two arguments are always required:
25.IP daemon
26A daemon process name. Typically, the last component of a daemon
27executable pathname.
28.IP client
29A host name or network address, or one of the `unknown' or `paranoid'
30wildcard patterns.
31.sp
32When a client host name is specified, \fItcpdmatch\fR gives a
33prediction for each address listed for that client.
34.sp
35When a client address is specified, \fItcpdmatch\fR predicts what
36\fItcpd\fR would do when client name lookup fails.
37.PP
38Optional information specified with the \fIdaemon@server\fR form:
39.IP server
40A host name or network address, or one of the `unknown' or `paranoid'
41wildcard patterns. The default server name is `unknown'.
42.PP
43Optional information specified with the \fIuser@client\fR form:
44.IP user
45A client user identifier. Typically, a login name or a numeric userid.
46The default user name is `unknown'.
47.SH OPTIONS
48.IP -d
49Examine \fIhosts.allow\fR and \fIhosts.deny\fR files in the current
50directory instead of the default ones.
51.IP "-i inet_conf"
52Specify this option when \fItcpdmatch\fR is unable to find your
53\fIinetd.conf\fR or \fItlid.conf\fR network configuration file, or when
54you suspect that the program uses the wrong one.
55.SH EXAMPLES
56To predict how \fItcpd\fR would handle a telnet request from the local
57system:
58.sp
59.ti +5
60tcpdmatch in.telnetd localhost
61.PP
62The same request, pretending that hostname lookup failed:
63.sp
64.ti +5
65tcpdmatch in.telnetd 127.0.0.1
66.PP
67To predict what tcpd would do when the client name does not match the
68client address:
69.sp
70.ti +5
71tcpdmatch in.telnetd paranoid
72.PP
73On some systems, daemon names have no `in.' prefix, or \fItcpdmatch\fR
74may need some help to locate the inetd configuration file.
75.SH FILES
76.PP
77The default locations of the \fItcpd\fR access control tables are:
78.PP
79/etc/hosts.allow
80.br
81/etc/hosts.deny
82.SH SEE ALSO
83.na
84.nf
85tcpdchk(8), tcpd configuration checker
86hosts_access(5), format of the tcpd access control tables.
87hosts_options(5), format of the language extensions.
88inetd.conf(5), format of the inetd control file.
89tlid.conf(5), format of the tlid control file.
90.SH AUTHORS
91.na
92.nf
93Wietse Venema (wietse@wzv.win.tue.nl),
94Department of Mathematics and Computing Science,
95Eindhoven University of Technology
96Den Dolech 2, P.O. Box 513,
975600 MB Eindhoven, The Netherlands
98\" @(#) tcpdmatch.8 1.5 96/02/11 17:01:35
Note: See TracBrowser for help on using the repository browser.