sffinger(1) [hpux man page]

tryfrom(1)						      General Commands Manual							tryfrom(1)

NAME

       tryfrom, sffinger - utility programs for TCP Wrappers

SYNOPSIS

DESCRIPTION

   tryfrom
       This  program  identifies  the  end-point details related to a connection.  This program must be called via a remote shell command as shown
       below.  It is used to find out if the hostname and the address are properly recognized, and also if the username lookup works properly.

       prints the following output when it is invoked:

       The information related to the client describes how the remote host recognizes the client in terms of address, name  and  user  name.   The
       information related to the server gives the remote host's details.

       See hosts_access(5) manual page for more information on expressions.

   sffinger
       This  is  a wrapper program to the finger(1) client which offers better protection against the possible damage from data sent by the remote
       server.	This command accepts all the options supported by finger(1).

       It is recommended to use this program in the implementation of traps in the access control language of and See hosts_access(5) man page for
       more information on setting traps.

       This  program  restricts  each line length to 128 bytes and total response to a maximum of 100000 bytes.  uses 60 seconds time-out value in
       getting the response from the remote host's server.

AUTHOR

       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

SEE ALSO

       finger(1), tcpd(1M), hosts_access(5).

																	tryfrom(1)

TCPDMATCH(8)						      System Manager's Manual						      TCPDMATCH(8)

NAME

       tcpdmatch - tcp wrapper oracle

SYNOPSYS

       tcpdmatch [-d] daemon client

       tcpdmatch [-d] 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 identifies 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 prediction 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 directory instead of the default ones.

EXAMPLES

       To predict how tcpd would handle a telnet request from the local system:

	    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

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

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)