GPG Keys encrypt & sign data. If an expiration date was set when a key was generated, it will eventually expire. Some of you may have encountered an issue, stating that your Bytemark GPG Keys have expired. If you are receiving a similar error (see below) when updating / installing a Bytemark package, you need to update your registered Bytemark GPG Keys.
GPG error: https://secure.bytemark.co.uk/key/repositories-2014.key "Bytemark_Key": The following signatures were invalid: KEYEXPIRED "key_id"
The steps required to update your keys vary slightly, depending on what distribution you are running. Please follow the relevant section below to update your expired keys.
Debian / Ubuntu / Symbiosis
Please run the following command to retrieve, install & update the newly-registered Bytemark GPG Keys:
wget -q -O - https://secure.bytemark.co.uk/key/repositories-2014.key | sudo apt-key add -; sudo apt-get update
You can now run the following command to list all of your GPG Keys and confirm that the newly registered key “Bytemark Hosting automatic repository signing key (2014)” has been imported successfully. Ensure that the expiration date for the key is 10 years in the future.
sudo apt-key list
CentOS
Please run the following command to retrieve, install & update the newly registered Bytemark GPG Keys:
sudo rpm --import https://secure.bytemark.co.uk/key/repositories-2014.key; sudo yum update
You can now enter the following command to list your GPG Keys and confirm that the newly registered key “Bytemark Hosting automatic repository signing key (2014)” has been imported & added. The expiration date for your new GPG key should 10 years from the current date.
sudo rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE}\t%{SUMMARY}\n'
Windows & Managed Servers
You are not required to update GPG keys on Windows or Managed servers.