Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-6844: How to determine the active ciphers on Centrify-enabled OpenSSH

Centrify DirectControl ,  

4 May,16 at 09:34 PM

Applies To: All versions of Centrify-Enabled OpenSSH on all platforms

Question:
Is there a way to determine the active ciphers on a running Centrify-enabled OpenSSH server?

Answer:
The active ciphers can be configured as needed in Centrify-enabled OpenSSH using the same parameters used on stock OpenSSH which it is based on.  Because the roots of Centrify-enabled OpenSSH are in the stock version it is bound by the same design parameters. As a result there is no simple way to determine the active ciphers aside from viewing what's defined in the sshd_config file.

The best options to determine this information is to:
a)  Set the appropriate parameters manually in the sshd_config file as per KB-2757: SSHD security cipher configuration

or

b)  Enable sshd debug and view the generated log file.
/usr/share/centrifydc/sbin/sshd –ddde –p 2022 > sshd.log 2>&1

Start sshd demon in debug mode, wait for few seconds, then stop the process. Review the log that is created. Near the top of the file you should see the active ciphers.  
This information comes from: 
KB-4276: How to enable SSH trace and Putty logs

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleKB-6041: How to show current license type in use by adclient? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6731: Impact of Badlock (CVE-2016-0128/CVE-2016-2118) on Centrify-Enabled Samba