Updating gpg key ubuntu


03-Feb-2018 17:15

Then, feed the key to apt-key with sudo apt-key add I encountered the same issue and the only solution I found, perhaps due to a firewall, was to use the helpful Y PPA Manager.

The two steps below outline has worked on Ubuntu 15.04.

This change to the GPG signing key affects both Puppet Enterprise users and open source Puppet users.

If you're using Puppet Enterprise, you'll be getting the new key in the next release, or if you manually update your version of puppet-agent, you'll get it then.

updating gpg key ubuntu-55

the dating scene

If you’re already setting up your repos using the puppetlabs-release or puppetlabs-release-pc1 packages, this is going to be the easiest way to get the updated key.newrelic-sysmond Automation tools like Ansible will also refuse to install newrelic-sysmond.Hi @tomas1, Did you Trust the New Relic GPG key during the installation process?For example, apt will remove SHA1 support: Teams/Apt/Sha1Removal - Debian Wiki So we have updated Treasure Agent's GPG key for deb/rpm to drop SHA1 based signing.

It means you need to update imported old GPG key before td-agent update.

$ curl --remote-name --location https://yum.puppetlabs.com/RPM-GPG-KEY-puppet $ gpg --keyid-format 0x LONG --with-fingerprint ./RPM-GPG-KEY-puppet pub 4096R/0x7F438280EF8D349F 2016-08-18 Puppet, Inc. Release Key) $ curl --remote-name --location https://apt.puppetlabs.com/DEB-GPG-KEY-puppet $ gpg --keyid-format 0x LONG --with-fingerprint ./DEB-GPG-KEY-puppet pub 4096R/0x7F438280EF8D349F 2016-08-18 Puppet, Inc. Release Key) Hopefully this helps get you up and running with our new GPG signing key.