|
Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!
TCPDMATCH(8) TCPDMATCH(8)
NAME
tcpdmatch - tcp wrapper oracle
SYNOPSYS
tcpdmatch [-d] [-i inet_conf] daemon client
tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client
DESCRIPTION
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 identi-
fies the matched rule. In addition, it displays the optional shell com-
mands or options in a pretty-printed format; this makes it easier for
you to spot any discrepancies between what you want and what the pro-
gram understands.
ARGUMENTS
The following two arguments are always required:
daemon A daemon process name. Typically, the last component of a daemon
executable pathname.
client A host name or network address, or one of the `unknown' or
`paranoid' wildcard patterns.
When a client host name is specified, tcpdmatch gives a predic-
tion for each address listed for that client.
When a client address is specified, tcpdmatch predicts what tcpd
would do when client name lookup fails.
Optional information specified with the daemon@server form:
server A host name or network address, or one of the `unknown' or
`paranoid' wildcard patterns. The default server name is
`unknown'.
Optional information specified with the user@client form:
user A client user identifier. Typically, a login name or a numeric
userid. The default user name is `unknown'.
OPTIONS
-d Examine hosts.allow and hosts.deny files in the current direc-
tory instead of the default ones.
-i inet_conf
Specify this option when tcpdmatch is unable to find your
inetd.conf or tlid.conf network configuration file, or when you
suspect that the program uses the wrong one.
EXAMPLES
To predict how tcpd would handle a telnet request from the local sys-
tem:
tcpdmatch in.telnetd localhost
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.
FILES
The default locations of the tcpd access control tables are:
/etc/hosts.allow
/etc/hosts.deny
SEE ALSO
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.
AUTHORS
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
TCPDMATCH(8)
Man(1) output converted with
man2html and wrapped by fishsponge
This page was generated on Sat Sep 8 16:40:30 GMT 2007
|
Your favourite pages:
No pages logged yet.
Trying to save cookie... Top 10 most popular pages:
svn man page (6164 hits)
(FreeBSD 6.2)
sqlite3 man page (5598 hits)
(openSUSE 10.2)
adv_cap_autoneg man page (5045 hits)
(Solaris 10 11_06)
CPAN man page (4791 hits)
(Suse Linux 10.1)
ssh man page (4439 hits)
(Suse Linux 10.1)
ssh-socks5-proxy-connect man page (3525 hits)
(Solaris 10 11_06)
signal man page (3395 hits)
(Suse Linux 10.1)
netcat man page (3383 hits)
(Suse Linux 10.1)
pprosetup man page (2890 hits)
(Solaris 10 11_06)
startproc man page (2739 hits)
(Suse Linux 10.1)
|
Man Pages 
