HP-UX Secure Shell Getting Started Guide

• The host name substitutes for %h
• The port number substitutes for %p
NOTE: The CheckHostIP directive is not available for connections with a ProxyCommand.
PubkeyAuthentication
Use this directive to specify whether to use public-key authentication.
The default setting is YES.
For example:
PubkeyAuthentication yes
NOTE: This directive is available for the SSH-2 protocol only.
RemoteForward
Use this directive to specify that a TCP/IP port on the remote system must be forwarded over
the secure channel to the specified host and port from the local system. The first value must be
[bind_address:]port. The second value must be host:hostport. IPv6 addresses can be
specified by enclosing addresses in square brackets or by using the following syntax:
[bind_address/]port and host/hostport. You can also specify multiple forwardings on the
command line. Only the superuser can forward privileged ports.
If the bind_address is not specified, the default is to bind only to loopback addresses. If the
bind_address is a star (*) or an empty string, then the forwarding is requested to listen on all
interfaces. Specifying a remote bind_address succeeds only if the server’s GatewayPorts
directive is enabled. For more information, see sshd_config((5)).
By default, remote forward is not used.
For example:
RemoteForward localhost:5001 remote:23
RhostsRSAAuthentication
Use this directive to specify whether to use host-based authentication with RSA host
authentication.
NOTE: This option is available for the SSH-1 protocol only.
The default setting is no.
For example:
RhostsRSAAuthentication no
RSAAuthentication
Use this directive to specify whether to use RSA authentication. RSA authentication is attempted
only if the identity file exists, or an authentication agent is running.
The default setting is YES.
For example:
RSAAuthentication yes
NOTE: This directive is available for the SSH-1 protocol only.
SendEnv
Use this directive to specify which variables from the local environ must be sent to the server.
Variables are specified by name and can contain the wildcard characters (*) and (?). Multiple
environment variables can be separated by spaces or spread across multiple SendEnv directives.
92 Configuration Files and Directives