-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Expired GPG Key for Puppet 8 Repository #9550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have the same issue with Puppet 7 Repository.
|
same here |
Also seeing on Jammy |
Yes. key expired on April 6. |
You can use https://apt.puppet.com/DEB-GPG-KEY-future as it doesn't have an expiration date. For APT based OS (/etc/apt)
|
It seems like puppet-tools-release-*.deb files are need resigning with newer key, I keep getting errors with code like this: RUN curl -fsSL https://apt.puppet.com/DEB-GPG-KEY-future | sudo gpg -o /etc/apt/trusted.gpg.d/puppet.gpg --dearmor
RUN echo ok && \
curl --silent --show-error https://apt.puppet.com/puppet-tools-release-focal.deb --output /tmp/puppet-tools-release.deb && \
dpkg -i /tmp/puppet-tools-release.deb && \
apt update && \
apt -y install puppet-bolt Error log:
|
Hi, finally installed with
|
They have released new keyring and new puppet package files |
I have the same problem? Is there an official solution? $ wget https://apt.puppetlabs.com/puppet6-release-xenial.deb
$ sudo dpkg -i puppet6-release-xenial.deb
$ sudo apt-get update
Get:1 http://apt.puppetlabs.com xenial InRelease [144 kB]
Ign:1 http://apt.puppetlabs.com xenial InRelease
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:5 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 144 kB in 0s (192 kB/s)
Reading package lists... Done
W: GPG error: http://apt.puppetlabs.com xenial InRelease: The following signatures were invalid: KEYEXPIRED 1743975562 KEYEXPIRED 1743975562 KEYEXPIRED 1743975562
W: The repository 'http://apt.puppetlabs.com xenial InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
|
I’m currently encountering an issue with the Puppet 8 repository where the GPG keys for package verification have expired. Specifically, the following keys are expired:
root@test:
# wget https://apt.puppet.com/puppet8-release-jammy.deb# dpkg-deb -x puppet8-release-jammy.deb /tmp/package-extractedroot@test:
root@test:~# apt-key add /tmp/package-extracted/etc/apt/trusted.gpg.d/puppet8-keyring.gpg
pub rsa4096 2019-04-08 [SC] [expired: 2025-04-06]
D681 1ED3 ADEE B844 1AF5 AA8F 4528 B6CD 9E61 EF26
uid [ expired] Puppet, Inc. Release Key (Puppet, Inc. Release Key) [email protected]
The text was updated successfully, but these errors were encountered: