Hi,
While running apt-get on my local system I encountered an error from APT complaining that the key had expired for keybase. Looking at the GPG key it does appear to have expired. Is there a new key published yet?
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://prerelease.keybase.io/deb stable InRelease: The following signatures were invalid: EXPKEYSIG 47484E50656D16C7 Keybase.io Code Signing (v1) <[email protected]>
W: Failed to fetch http://prerelease.keybase.io/deb/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 47484E50656D16C7 Keybase.io Code Signing (v1) <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.
pub rsa4096 2013-11-19 [SC] [expired: 2017-11-19]
222B 85B0 F90B E2D2 4CFE B93F 4748 4E50 656D 16C7
uid [ expired] Keybase.io Code Signing (v1) <[email protected]>
cc: @oconnor663
Looks like there was a warning message that I needed to update keybase to account for the expiring key :) please ignore and close as PEBCK issue.
Same issue as https://github.com/keybase/client/issues/9626.
Unfortunately as far as I can tell, none of these bug reports or the docs page about this are currently reachable via google.
thanks for the link to the docs @oconnor663.
how often will this happen in the future?
The current version of the signing key doesn't expire until 2027. Hopefully by then the world will have moved on to a packaging system that doesn't depend on PGP :)
"hopefully the world will have moved on from ipv4" - 1995 internet chatroom talk
I use ipv9, idk about you guys.
Also, I use keybase to sign all my packages. You ever heard of it? :-P
Most helpful comment
Unfortunately as far as I can tell, none of these bug reports or the docs page about this are currently reachable via google.