HP-UX Secure Shell Getting Started Guide HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 (5900-3142, June 2013)

Host
Use this directive to specify restricts on the declarations (up to the next Host keyword) to be only
for those hosts that match one of the string pattern given after the keyword. A single * as a pattern
can be used to provide global defaults for all hosts. The host is the hostname argument given on
the command line (that is, the name is not converted to a canonicalized host name before matching).
A pattern entry may be negated by prefixing it with an exclamation mark (!). If a negated entry is
matched, then the Host entry is ignored, regardless of whether any other patterns on the line match.
Negated matches are therefore useful to provide exceptions for wildcard matches.
The default value is *.
For example:
Host *
AddressFamily
Use this directive to specify the address family to be used when connecting to the server. Following
are the valid values:
• any
• inet (IPv4 only)
• inet6(IPv6 only)
The default value is any.
For example:
AddressFamily inet
BatchMode
Use this directive to specify whether passphrase or password querying is disabled. Use this directive
with scripts and other batch jobs where no user is present to supply a password.
The default setting is no.
For example:
BatchMode no
BindAddress
Use this directive to specify the address on the local host as the source address for the connection.
Use this directive on systems with more than one address.
The default setting is the loopback address.
For example:
BindAddress yes
NOTE: The BindAddress directive does not work if the UsePrivilegedPort directive is set
to yes.
ChallengeResponseAuthentication
Use this directive to specify whether to use challenge-response (keyboard-interactive) authentication.
The default setting is yes.
For example:
ChallengeResponseAuthentication yes
CheckHostIP
Use this directive to specify whether to check the host IP address in the known_hosts file. This
enables HP-UX Secure Shell to detect whether a host key was modified because of DNS spoofing.
If the option is set to no, the check is not executed.
84 Configuration Files and Directives