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.