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-4503: Centrify sshd will not start after an upgrade

Centrify DirectControl ,  

12 April,16 at 11:13 AM

Applies to:
 
Centrify DirectControl 5.1.3/Centrify-enabled OpenSSH 
 
Question:
 
If an existing /etc/centrifydc/ssh/sshd_config file has a Match statement at the end of the file (as required) and if an upgrade of Centrify DirectControl
(from any version) to Centrify DirectControl 5.1.3 is performed, sshd will not start and the below error message is reported when a syntax check is performed.
 
root@rhel6 home]# /usr/share/centrifydc/sbin/sshd -t

/etc/centrifydc/ssh/sshd_config line 120: Directive 'UsePrivilegeSeparation' is not allowed within a Match block
 
Snippet of sshd_config file prior to upgrade:
 
Match group sftponly
ForceCommand /usr/share/centrifydc/libexec/sftp-server

and after upgrade:
 
Match group sftponly
ForceCommand /usr/share/centrifydc/libexec/sftp-server
UsePrivilegeSeparation sandbox # Default for new installations.

Answer:
 
This is a known issue in Centrify DirectControl Openssh ssh-mergeconf script where the upgrade appends a line in the end of the
sshd_config file as shown below.
 
"UsePrivilegeSeparation sandbox # Default for new installations"
 
The sshd_config Match blocks man pages:

If all of the criteria on the Match line are satisfied, the keywords on the following lines override those set in the global section of the config file, until either another Match line or the end of the file. If there are Match blocks, UsePrivilegeSeparation settings is considered part of the last Match block rather than global settings. Sshd will cannot start.

Customers are requested to manually move (or use a secondary script) the "Match group/user" line to the bottom of the line in the file and sshd will start normally.
 
This issue is fixed in a future release.

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

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-9059: What is the difference between the 2 Centrify-SSHD service on Solaris after upgrading Centrify? articleKB-8047: sshd_config option 'Match Host' stops working after upgrading to Centrify Suite 2016.1 articleKB-6511: After upgrade to 2016 Centrify DirectControl and Centrify-Enabled OpenSSH, PKI based SSH login fails 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-3925: How to add Centrify parameter to a group policy