Paper key backup not accepted
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Hi there,
I recently realised that I forgot my keybase passphrase and the passphrase to my main device (yikes). :(
Following advice from the keybase website, I ran keybase passphrase recover in order to reset the passphrase using my backup paper key.
Unfortunately, when I enter my paper key, I get:
[22:01:07]florent@mba:~/$ keybase passphrase recover
Password recovery will put your account on probation for 5 days.
You won't be able to perform certain actions, like revoking devices.
Continue with password recovery? (type 'YES' to confirm): YES
Pick a new strong passphrase (12+ characters):
Please reenter your new passphrase for confirmation:
Please enter a paper backup key passphrase for florentdelannoy:
▶ ERROR Bad passphrase: no matching paper backup keys found.
I believe this is an error because this paper key exists, and when I key in random garbage instead of my key, I get a different error:
[21:59:07]florent@mba:~/$ keybase passphrase recover
Password recovery will put your account on probation for 5 days.
You won't be able to perform certain actions, like revoking devices.
Continue with password recovery? (type 'YES' to confirm): YES
Pick a new strong passphrase (12+ characters):
Please reenter your new passphrase for confirmation:
Please enter a paper backup key passphrase for florentdelannoy:
▶ ERROR Invalid key version
Using keybase version 1.0.15
If it helps, my log id: 590228bc89bed2ff7dd01a1c
Cheers,
Florent
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
Start with the keybase passphrase recover flow and compare the reported errors for the paper key and random input, using version 1.0.15 and log id 590228bc89bed2ff7dd01a1c. The issue is done when a valid paper backup key is accepted for recovery while invalid input continues to produce an appropriate error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100