SSH Reference Manual

Suppressing the Banner printed by Clients
When SSH[OSS] and SFTP[OSS] clients print a banner containing the version and name of the ssh client, e.g. like:
comForte SSH client version T9999G06_22Jan2014_SSH_0097
This banner can be suppressed by setting Boolean parameter SUPPRESSCLIENTBANNER in the client environment,
i.e. via PARAM in a TACL environment:
PARAM SUPPRESSCLIENTBANNER TRUE
and via environment variable in OSH environment:
export SUPPRESSCLIENTBANNER=TRUE
Automating the SFTP/SSH clients
SSH[OSS] and SFTP[OSS] clients are normally used directly by humans but sometimes it is required to automate the
control of these clients, e.g. by setting IN and OUT of a client to a controlling program or script. In this case it is helpful
to differentiate between messages printed by the client during startup/connection phase and other data. The following
new parameters must be set in the client environment (PARAM under TACL or environment variable under OSH).
Parameter Meaning
SSHERRORPREFIX String that is printed as prefix for an error message
SSHINFOPREFIX String that is printed as prefix for informational messages
SSHQUERYPREFIX String that is printed as prefix for queries (prompts)
For each of these parameters a corresponding option is supported by the clients as shown below:
Option Meaning
-H "<errorprefix>" String that is printed as prefix for an error message
-J "<infoprefix>" String that is printed as prefix for informational messages
-K "<queryprefix>" String that is printed as prefix for queries (prompts)
FILE I/O Parameters for SFTP/SFTPOSS
File operations executed on local disks can be influenced by setting specific parameters in the environment of SFTP and
SFTPOSS clients.
Currently the parameters set for the SSH2 process are not propagated to the SFTP/SFTPOSS clients, i.e. without setting
the parameters in the client environment the default values for these parameters are used. Guardian file attributes can be
exchanged between sftp client and sftp server. But other settings must be configured independently on both the client and
the server side. This must happen in a non-conflicting way. For example: If client and server are using different
delimiters to indicate the end of a record (relevant for edit files and structured files), then the result of a file transfer will
not be as expected.
For details on these parameters, please see description in section "SSH2 Parameter Reference" in chapter "Configuring
and Running SSH2"). The following table shows which parameter can be used in the client environment when sending or
receiving files.
HP NonStop SSH Reference Manual SSH and SFTP Client Reference • 219