GPG

YUM GPG keys

NOTE: If you installed fdio/hicn with our Bash script, Chef cookbook, or Puppet module the GPG key is automatically installed. There is nothing additional you need to do.

GPG signature info

fdio/hicn has its YUM metadata signed with fdio-hicn-F4B18BE22DD07645.pub.gpg.

Important notes

There are two types of GPG keyrings used on RPM-based systems:

  1. RPM's GPG keyring. This keyring is used for verifying signatures on RPM packages.
  2. YUM's GPG keyring. This keyring is used for verifying signatures on repository metadata. There is one keyring per repository on the system.

The YUM GPG keyring (number 2 above) is the keyring that the information on this page refers to.

Import GPG key for fdio/hicn

To import a GPG key to verify YUM metadata, you must create a repo config with the GPG key URL. This is done automatically with all of our install methods.

If you'd like to do this manually for fdio/hicn, follow the instructions on the manual install page

Remove GPG key for fdio/hicn

Unfortunately GPG key removal is not particularly user friendly.

  1. Check your /etc/yum.conf file and note the value of persistdir. If persistdir is not set, you can assume it is /var/lib/yum.
  2. Determine which CPU architecture the repo has been installed for: i386 for 32-bit systems and x86_64 for 64-bit systems.
  3. Determine the verison number of the CentOS or Red Hat you are running (5, 6, or 7).
  4. Replace x86_64 and 7 in the following command with your CPU architecture and CentOS or Red Hat version:
  5. gpg --homedir /var/lib/yum/repos/x86_64/7/fdio_hicn/gpgdir --delete-key F4B18BE22DD07645