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-8813: Warning message “dangerous-command” when running rpmlint against DirectControl package

Authentication Service ,  

13 June,17 at 07:16 PM

Question:

Upon running the Centrify rpmlint command against Centrify DirectControl package, it may show the following warning message.
 
CentrifyDC.x86_64: W: dangerous-command-in-%pre chmod
 
What is the significance and impact of this warning message on Centrify DirectControl?

Answer:
 
Centrify has researched this command and determined that the command is flagging our use of chmod in our package script. This is being done to safeguard the Centrify installation directory and in our conclusion is a safe action given the circumstances. As reported by the output, it is a warning message only intended to notify and not reported as an error level message.
 
 
For reference here is what will happen when you run the rpm command with a specific Centrify package.
 
$ rpm -qp --scripts CentrifyDC-5.4.1-rhel4.x86_64.rpm | grep chmod
 
Observing the following output broken down into three different parts with clarification.
 
First part, this is to ensure integrity of the run time settings directory
    chmod 755 /var/centrifydc >> ${LOG_FILE} 2>> ${LOG_FILE}
 
Second part, these are to ensure the integrity of the machine GP settings directory (${REG_DIR} = /var/Centrifydc/reg)
    find ${REG_DIR}/machine/secedit/ -type d -exec chmod 700  '{}' \;
    find ${REG_DIR}/machine/secedit/ -type f -exec chmod 600  '{}' \;
    find ${REG_DIR}/machine/software/ -type d -exec chmod 700  '{}' \;
    find ${REG_DIR}/machine/software/ -type f -exec chmod 600  '{}' \;
    chmod 600 ${REG_DIR}/machine/applied_policies
    chmod 744 ${REG_DIR}/machine/gp.report
 
Third part, these are to ensure the integrity of the user GP settings directory (${REG_DIR}/users/)
 
    find $user/* -type d -exec chmod 700  '{}' \;
    find $user/ -type f -exec chmod 600  '{}' \;
    chmod 755 /var/centrifydc >> ${LOG_FILE}

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

Related Articles

 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-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-3925: How to add Centrify parameter to a group policy articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part III