Penguin
Recent Changes
Blame: tcpdmatch(8)
EditPageHistoryDiffInfoLikePages
Annotated edit history of tcpdmatch(8) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 TCPDMATCH
2 !!!TCPDMATCH
3 NAME
4 SYNOPSYS
5 DESCRIPTION
6 ARGUMENTS
7 OPTIONS
8 EXAMPLES
9 FILES
10 SEE ALSO
11 AUTHORS
12 ----
13 !!NAME
14
15
16 tcpdmatch - tcp wrapper oracle
17 !!SYNOPSYS
18
19
20 tcpdmatch [[-d] [[-i inet_conf] daemon client
21
22
23 tcpdmatch [[-d] [[-i inet_conf] daemon[[@server]
24 [[user@]client
25 !!DESCRIPTION
26
27
28 ''tcpdmatch'' predicts how the tcp wrapper would handle a
29 specific request for service. Examples are given
30 below.
31
32
33 The program examines the ''tcpd'' access control tables
34 (default ''/etc/hosts.allow'' and ''/etc/hosts.deny'')
35 and prints its conclusion. For maximal accuracy, it extracts
36 additional information from your ''inetd'' or ''tlid''
37 network configuration file.
38
39
40 When ''tcpdmatch'' finds a match in the access control
41 tables, it identifies the matched rule. In addition, it
42 displays the optional shell commands or options in a
43 pretty-printed format; this makes it easier for you to spot
44 any discrepancies between what you want and what the program
45 understands.
46 !!ARGUMENTS
47
48
49 The following two arguments are always
50 required:
51
52
53 daemon
54
55
56 A daemon process name. Typically, the last component of a
57 daemon executable pathname.
58
59
60 client
61
62
63 A host name or network address, or one of the `unknown' or
64 `paranoid' wildcard patterns.
65
66
67 When a client host name is specified, ''tcpdmatch'' gives
68 a prediction for each address listed for that
69 client.
70
71
72 When a client address is specified, ''tcpdmatch''
73 predicts what ''tcpd'' would do when client name lookup
74 fails.
75
76
77 Optional information specified with the ''daemon@server''
78 form:
79
80
81 server
82
83
84 A host name or network address, or one of the `unknown' or
85 `paranoid' wildcard patterns. The default server name is
86 `unknown'.
87
88
89 Optional information specified with the ''user@client''
90 form:
91
92
93 user
94
95
96 A client user identifier. Typically, a login name or a
97 numeric userid. The default user name is
98 `unknown'.
99 !!OPTIONS
100
101
102 -d
103
104
105 Examine ''hosts.allow'' and ''hosts.deny'' files in
106 the current directory instead of the default
107 ones.
108
109
110 -i inet_conf
111
112
113 Specify this option when ''tcpdmatch'' is unable to find
114 your ''inetd.conf'' or ''tlid.conf'' network
115 configuration file, or when you suspect that the program
116 uses the wrong one.
117 !!EXAMPLES
118
119
120 To predict how ''tcpd'' would handle a telnet request
121 from the local system:
122
123
124 tcpdmatch in.telnetd localhost
125
126
127 The same request, pretending that hostname lookup
128 failed:
129
130
131 tcpdmatch in.telnetd 127.0.0.1
132
133
134 To predict what tcpd would do when the client name does not
135 match the client address:
136
137
138 tcpdmatch in.telnetd paranoid
139
140
141 On some systems, daemon names have no `in.' prefix, or
142 ''tcpdmatch'' may need some help to locate the inetd
143 configuration file.
144 !!FILES
145
146
147 The default locations of the ''tcpd'' access control
148 tables are:
149
150
151 /etc/hosts.allow
152 /etc/hosts.deny
153 !!SEE ALSO
154
155
156 tcpdchk(8), tcpd configuration checker
157 hosts_access(5), format of the tcpd access control tables.
158 hosts_options(5), format of the language extensions.
159 inetd.conf(5), format of the inetd control file.
160 tlid.conf(5), format of the tlid control file.
161 !!AUTHORS
162
163
164 Wietse Venema (wietse@wzv.win.tue.nl),
165 Department of Mathematics and Computing Science,
166 Eindhoven University of Technology
167 Den Dolech 2, P.O. Box 513,
168 5600 MB Eindhoven, The Netherlands
169 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.