{"id":3618,"date":"2022-12-20T17:09:10","date_gmt":"2022-12-20T20:09:10","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/tcpdmatch-man8\/"},"modified":"2022-12-20T17:09:10","modified_gmt":"2022-12-20T20:09:10","slug":"tcpdmatch-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/tcpdmatch-man8\/","title":{"rendered":"TCPDMATCH (man8)"},"content":{"rendered":"

TCPDMATCH<\/h1>\n

NAME<\/a>
SYNOPSYS<\/a>
DESCRIPTION<\/a>
ARGUMENTS<\/a>
OPTIONS<\/a>
EXAMPLES<\/a>
FILES<\/a>
SEE ALSO<\/a>
AUTHORS<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

tcpdmatch \u2212 tcp wrapper oracle<\/p>\n

SYNOPSYS <\/a> <\/h2>\n

tcpdmatch [-d] [-i inet_conf] daemon client<\/p>\n

tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

tcpdmatch<\/i> predicts how the tcp wrapper would handle a specific request for service. Examples are given below.<\/p>\n

The program examines the tcpd<\/i> access control tables (default \/etc\/hosts.allow<\/i> and \/etc\/hosts.deny<\/i>) and prints its conclusion. For maximal accuracy, it extracts additional information from your inetd<\/i> or tlid<\/i> network configuration file.<\/p>\n

When tcpdmatch<\/i> 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.<\/p>\n

ARGUMENTS <\/a> <\/h2>\n

The following two arguments are always required:<\/p>\n\n\n\n
<\/td>\n\n

daemon<\/p>\n<\/td>\n

<\/td>\n\n

A daemon process name. Typically, the last component of a daemon executable pathname.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

client<\/p>\n<\/td>\n

<\/td>\n\n

A host name or network address, or one of the \u2018unknown\u2019 or \u2018paranoid\u2019 wildcard patterns.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

When a client host name is specified, tcpdmatch<\/i> gives a prediction for each address listed for that client.<\/p>\n

When a client address is specified, tcpdmatch<\/i> predicts what tcpd<\/i> would do when client name lookup fails.<\/p>\n

Optional information specified with the daemon@server<\/i> form:<\/p>\n\n\n
<\/td>\n\n

server<\/p>\n<\/td>\n

<\/td>\n\n

A host name or network address, or one of the \u2018unknown\u2019 or \u2018paranoid\u2019 wildcard patterns. The default server name is \u2018unknown\u2019.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

Optional information specified with the user@client<\/i> form:<\/p>\n\n\n
<\/td>\n\n

user<\/p>\n<\/td>\n

<\/td>\n\n

A client user identifier. Typically, a login name or a numeric userid. The default user name is \u2018unknown\u2019.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

OPTIONS <\/a> <\/h2>\n\n\n
<\/td>\n\n

-d<\/p>\n<\/td>\n

<\/td>\n\n

Examine hosts.allow<\/i> and hosts.deny<\/i> files in the current directory instead of the default ones.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

-i inet_conf<\/p>\n

Specify this option when tcpdmatch<\/i> is unable to find your inetd.conf<\/i> or tlid.conf<\/i> network configuration file, or when you suspect that the program uses the wrong one.<\/p>\n

EXAMPLES <\/a> <\/h2>\n

To predict how tcpd<\/i> would handle a telnet request from the local system:<\/p>\n

tcpdmatch in.telnetd localhost<\/p>\n

The same request, pretending that hostname lookup failed:<\/p>\n

tcpdmatch in.telnetd 127.0.0.1<\/p>\n

To predict what tcpd would do when the client name does not match the client address:<\/p>\n

tcpdmatch in.telnetd paranoid<\/p>\n

On some systems, daemon names have no \u2018in.\u2019 prefix, or tcpdmatch<\/i> may need some help to locate the inetd configuration file.<\/p>\n

FILES <\/a> <\/h2>\n

The default locations of the tcpd<\/i> access control tables are:<\/p>\n

\/etc\/hosts.allow
\/etc\/hosts.deny<\/p>\n

SEE ALSO <\/a> <\/h2>\n

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.<\/p>\n

AUTHORS <\/a> <\/h2>\n

Wietse 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<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

tcpdmatch \u2212 tcp wrapper oracle <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,734],"class_list":["post-3618","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-tcpdmatch"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3618","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3618"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3618\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3618"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3618"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3618"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}