Encryption Tab - Advanced Secure Shell Settings

Getting there

From the Administrative Console and X Manager

(Administrative Console only) Click the Domain Definitions tab.
Under X Clients on the left, select a client definition.
Set Connection Method to Secure Shell.
Click the Advanced button.
Click the Encryption tab.

Use the settings on the Encryption tab to configure the encryption algorithms available for use by the Secure Shell connection, and define the order of preference for their use.

Use the arrow buttons to move a selected algorithm up or down in the list.

Cipher Algorithms	Specify one or more cipher A cipher is an encryption algorithm. The cipher you select determines which mathematical algorithm is used to obscure the data being sent after a successful Secure Shell connection has been established. algorithms to use for encrypting the session, in order of preference. The cipher used for a session is the first item in this list that is also supported by the server. NOTE:If FIPS mode is enabled, the list of available cipher algorithms is restricted to FIPS-compatible algorithms.
HMAC Algorithms	Specify a series of HMAC (hash-based message authentication code) algorithms, in order of preference. Secure Shell connections use HMACs to ensure data integrity. The client and server independently compute a hash for each packet of transferred data. If the message has changed in transit, the hash values are different and the packet is rejected. The HMAC used for a session is the first item in this list that is also supported by the server. NOTE:If FIPS mode is enabled, the list of available MAC algorithms is restricted to FIPS-compatible algorithms.
Key Exchange Algorithms	Specify one or more key exchange algorithms by which the client and server negotiate a shared session key, in order of preference.

NOTE:For 16-1 SP1 Update 1 and higher, Reflection X Advantage primarily uses the Bouncy Castle crypto provider. X Manager for Domains uses the Bouncy Castle provider for all connections when the product is configured for FIPS mode. However, when X Manager for Domains is not in FIPS mode and an SSH connection attempts to use an encryption algorithm that is not supported by the Bouncy Castle FIPS library, the Sun JCE (Java Cryptography Extension) provider is used. X Manager Standalone mode uses the Bouncy Castle crypto provider for all encryption algorithms, regardless of FIPS mode.