Applies to: 

Server Suite 2015.1 and later. 


Question: 

Does Centrify provide GPG key to ensure RPMs are not corrupted or tampered with? 


Answer: 

Starting Server Suite 2015.1, RPMs are signed with a GPG key pair. GPG public key is provided in our download center. This key can be imported just like any other GPG keys: 
 

[root@centos67 ~]$ rpm --checksig /tmp/2016.1/centrify*.rpm
/tmp/2016.1/centrifyda-3.3.1-rhel4-x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#b65eca48)
/tmp/2016.1/centrifydc-5.3.1-rhel4-x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#b65eca48)
/tmp/2016.1/centrifydc-ldapproxy-5.3.1-rhel4-x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#b65eca48)
/tmp/2016.1/centrifydc-nis-5.3.1-rhel4-x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#b65eca48)
/tmp/2016.1/centrifydc-openssh-7.2p2-5.3.1-rhel4-x86_64.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#b65eca48)
[root@centos67 ~]$ rpm --import RPM-GPG-KEY-centrify
[root@centos67 ~]$ rpm --checksig /tmp/2016.1/centrify*.rpm
/tmp/2016.1/centrifyda-3.3.1-rhel4-x86_64.rpm: (sha1) dsa sha1 md5 gpg OK
/tmp/2016.1/centrifydc-5.3.1-rhel4-x86_64.rpm: (sha1) dsa sha1 md5 gpg OK
/tmp/2016.1/centrifydc-ldapproxy-5.3.1-rhel4-x86_64.rpm: (sha1) dsa sha1 md5 gpg OK
/tmp/2016.1/centrifydc-nis-5.3.1-rhel4-x86_64.rpm: (sha1) dsa sha1 md5 gpg OK
/tmp/2016.1/centrifydc-openssh-7.2p2-5.3.1-rhel4-x86_64.rpm: (sha1) dsa sha1 md5 gpg OK