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

This ProxyCommand string is executed with /bin/sh. In the previous command string, the following
substitutions occur:
• 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.
RekeyLimit
Use this directive to specify the maximum amount of data that may be transmitted before the session
key is renegotiated. The argument is the number of bytes, with an optional suffix of K, M, or G to
indicate Kilobytes, Megabytes, or Gigabytes, respectively.
The default is between 1G and 4G, depending on the cipher.
For example:
RekeyLimit 1G
NOTE: This directive is available for the protocol version 2 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
RequestTTY
Use this directive to specify whether to request a pseudo-tty for the session. The argument may be
one of the following:
no never request a TTY
yes always request a TTY when standard input is a TTY
force always request a TTY
auto request a TTY when opening a login session.
This option is similar to the -t and -T flags for ssh(1).
For example:
RequestTTY auto
Client Configuration Directives 95