HP-UX Secure Shell Getting Started Guide

The default is not to send any environment variables.
For example:
SendEnv DISPLAY
Where:
DISPLAY is set as follows on the HP-UX Secure Shell client system:
$ export DISPLAY=john.users.com:0.0
NOTE: Environment passing is available for the SSH-2 protocol only. The server must also
support environment passing, and it must be configured to accept environment variables.
For more information on configuring the server, see “AcceptEnv” (page 67).
ServerAliveInterval
Use this directive to set a timeout interval value (in seconds) for a server. If no data has been
received from the server within the specified time, ssh sends a message through the encrypted
channel to request a response from the server.
NOTE: This directive is available for the SSH-2 protocol only.
The default setting is 0, indicating that no server alive messages are sent to the server.
For example:
ServerAliveInterval 0
ServerAliveCountMax
Use this directive to set the number of server alive messages that can be sent without ssh receiving
any messages back from the server.
Use this directive if the client or server depend on knowing when a connection is inactive.
If the number of server keep alive messages reaches the threshold, HP-UX Secure Shell disconnects
from the server, terminating the session.
The default setting is 3.
For example:
ServerAliveCountMax 3
NOTE: ServerAliveCountMax is different from TCPKeepAlive. Server alive messages are
sent through an encrypted channel and are not spoofable. Messages from the TCPKeepAlive
directive are spoofable.
StrictHostKeyChecking
Use this directive to specify whether HP-UX Secure Shell must add a new host to the $HOME/
.ssh/known_hosts file. StrictHostKeyChecking protects against Trojan horse attacks.
TIP: HP does not recommend using StrictHostKeyChecking when the /opt/ssh/etc/
ssh_known_hosts file is poorly maintained or connections to new hosts are made frequently.
If you use StrictHostKeyChecking, you must manually add all new hosts.
Following are the valid values of the StrictHostKeyChecking directive:
YES HP-UX Secure Shell does not automatically add host keys to the $HOME/.ssh/
known_hosts file and refuses to connect to hosts whose host key has changed.
no HP-UX Secure Shell automatically adds new host keys to the known_hosts file.
Client Configuration Directives 93