Modifying the SSH server profile
Modify the SSH server profile to define the cipher suites to negotiate SSH connections when the SSH server.
About this task
Each domain has a single SSH server profile.
- In the
defaultdomain, the SSH service is the only service that uses the SSH server profile. Never configure anything but management services in thedefaultdomain. - In an application domain, all SFTP server handlers in the domain use the SSH server profile.
You can specify a list of SSH cipher suites, key exchange (KEX) algorithms, and message
authentication code (MAC) algorithms in preferred order. The ciphers, KEX algorithms, and MAC
algorithms are used to negotiate SSH connections with the remote SSH server. When
you specify no ciphers or algorithms, the default cipher suites are used. For more information, see
the documentation for the following commands.
The order of algorithms is important. The client sends its list of algorithms to the server. The server compares this list to its own list in order of preference. The first algorithm in the client list is chosen when supported by the server. The connection fails when no algorithm from the client matches an algorithm in the server list.
You can configure a banner message to send to users during SSH preauthentication phase, which
includes an SFTP command login. The message is displayed to the user before the login prompt by
enabling the setting of including an SSH preauthentication message and specifying the message. When
you define a custom CLI pre-login message, the SSH preauthentication message is displayed before the
CLI prelogin message. The following rules apply.
- When the setting is enabled with no message specified, the setting is disabled again.
- When the message is longer than the maximum length of 4096 characters, the message is truncated to 4096 characters.