keybase / keybase/client

Debian Signing Key Expired

Open
#9,632 9 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

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) <code@keybase.io>
W: Failed to fetch http://prerelease.keybase.io/deb/dists/stable/InRelease  The following signatures were invalid: EXPKEYSIG 47484E50656D16C7 Keybase.io Code Signing (v1) <code@keybase.io>
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) <code@keybase.io>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report contains no repository file or test entry point; start by checking the Debian repository signing-key publication and the expired Keybase.io Code Signing key shown in the apt-get output. Done means a replacement signing key is published and apt-get can verify the stable InRelease without the EXPKEYSIG error.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian
Domain
cryptography, release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.