keybase / keybase/client

Dropping PGP key via desktop app caused my graph to disappear

Open
#8,565 0 comments 0 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

Since I have changed PGP keys I attempted to drop my old key from keybase so there would be no confusion as to which key to use. (perhaps we should have a way to visually mark a key as expired?)

The side effect of this was that my entire trust graph is blank after dropping the key. This might be because that key was used to add all of my devices and initially rebuild my profile. This could also quite possibly be desired behavior since when keys are dropped keybase refers to it as a revocation of the key, which could cause the the key (and items verified by it) to no longer be trusted.

Let me know if there are any logs/proofs that would help if this is indeed a bug not a feature.

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

No files, tests, or entry points are named. Start by reproducing the desktop-app flow of dropping an old PGP key, then inspect how key revocation affects trust-graph loading. Done means determining whether a blank graph is intended and, if not, documenting the expected behavior and covering the regression with a test.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cryptography, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.