keybase / keybase/keybase-issues
Inconsistent Public Key
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I was trying to inspect my own public key to ensure it was updated correctly after editing it in Mac GPG Keychain. I see the correct key when on my keybase profile page in the browser (i.e. if I copy it into a file called public.asc, and run `gpg --list-packets public.asc` I see my edits), however when I run `keybase pull` the public key pulled down appears to be the original, unmodified one generated when I signed up to keybase.
Any ideas?
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the mismatch by comparing the keybase profile download with the output of `keybase pull`, then inspect the packet contents with `gpg --list-packets`. The issue names no source files or tests, so tracing the public-key pull path and defining the expected key version would be the first step. Done means `keybase pull` returns the edited public key consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100