1TCPDMATCH(8)                System Manager's Manual               TCPDMATCH(8)
2
3
4

NAME

6       tcpdmatch - tcp wrapper oracle
7

SYNOPSYS

9       tcpdmatch [-d] daemon client
10
11       tcpdmatch [-d] daemon[@server] [user@]client
12

DESCRIPTION

14       tcpdmatch  predicts how the tcp wrapper would handle a specific request
15       for service.  Examples are given below.
16
17       The  program  examines  the  tcpd  access   control   tables   (default
18       /etc/hosts.allow  and  /etc/hosts.deny) and prints its conclusion.  For
19       maximal accuracy, it extracts additional information from your inetd or
20       tlid network configuration file.
21
22       When  tcpdmatch  finds a match in the access control tables, it identi‐
23       fies the matched rule. In addition, it displays the optional shell com‐
24       mands  or  options in a pretty-printed format; this makes it easier for
25       you to spot any discrepancies between what you want and what  the  pro‐
26       gram understands.
27

ARGUMENTS

29       The following two arguments are always required:
30
31       daemon A daemon process name. Typically, the last component of a daemon
32              executable pathname.
33
34       client A host name or network address,  or  one  of  the  `unknown'  or
35              `paranoid' wildcard patterns.
36
37              When  a client host name is specified, tcpdmatch gives a predic‐
38              tion for each address listed for that client.
39
40              When a client address is specified, tcpdmatch predicts what tcpd
41              would do when client name lookup fails.
42
43       Optional information specified with the daemon@server form:
44
45       server A  host  name  or  network  address,  or one of the `unknown' or
46              `paranoid'  wildcard  patterns.  The  default  server  name   is
47              `unknown'.
48
49       Optional information specified with the user@client form:
50
51       user   A  client  user identifier. Typically, a login name or a numeric
52              userid.  The default user name is `unknown'.
53

OPTIONS

55       -d     Examine hosts.allow and hosts.deny files in the  current  direc‐
56              tory instead of the default ones.
57

EXAMPLES

59       To  predict  how tcpd would handle a telnet request from the local sys‐
60       tem:
61
62            tcpdmatch in.telnetd localhost
63
64       The same request, pretending that hostname lookup failed:
65
66            tcpdmatch in.telnetd 127.0.0.1
67
68       To predict what tcpd would do when the client name does not  match  the
69       client address:
70
71            tcpdmatch in.telnetd paranoid
72
73       On  some  systems,  daemon names have no `in.' prefix, or tcpdmatch may
74       need some help to locate the inetd configuration file.
75

FILES

77       The default locations of the tcpd access control tables are:
78
79       /etc/hosts.allow
80       /etc/hosts.deny
81

SEE ALSO

83       hosts_access(5), format of the tcpd access control tables.
84       hosts_options(5), format of the language extensions.
85

AUTHORS

87       Wietse Venema (wietse@wzv.win.tue.nl),
88       Department of Mathematics and Computing Science,
89       Eindhoven University of Technology
90       Den Dolech 2, P.O. Box 513,
91       5600 MB Eindhoven, The Netherlands
92
93
94
95
96                                                                  TCPDMATCH(8)
Impressum