Failed to parse public key at position 0, Bad key family: No key found
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
My log id: a6fc0a13730bc2dcb36ec71c
I'm having trouble logging into keybase on my mac. Neither the app nor the command line work. The error shown is:
▶ NOTICE Failed to parse public key at position 0
▶ ERROR Bad key family: No key found for 0111ed0fe109f952017700a18066e505f4ed056613d208f2e5cb0aafbd7cb7db95340a
I believe I am using a fairly old PGP key I made in 2004. As I have not read up on how to migrate to a new key, I'd like to continue using the one I have for a while longer. Can you tell from the log I sent you whether the key is the problem?
Disclaimer: I only installed keybase (and gpg2) today, I have my account since 2014 though.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the macOS app, command-line client, Keybase, and gpg2, but no source file, test, or entry point. Start by locating the public-key parsing and key-family error paths, then reproduce the supplied log case; the report does not define what a successful fix should be.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100