keybase rekey warning, cannot rekey
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
This issue appears to be reoccurring on a new device -
keybase/client#7629
I installed keybase on a new laptop and the app is prompting me to turn on another device or enter a paper key.
Neither of which appear to resolve the issue.
I get this from the command line -
keybase rekey status
TLFs need rekeying:
private/soulware
Devices that can rekey:
backup <redacted>
desktop macbook_q
mobile iphone
Running keybase rekey paper has no effect. I can enter the paper key but the issue persists.
Assuming logs will help so here you go -
keybase log send
------------
Success! Your log ID is:
c1439726bf1dc5c596b4921c
Here's a URL to submit new bug reports containing this ID:
https://github.com/keybase/client/issues/new?body=[write%20something%20useful%20and%20descriptive%20here]%0A%0Amy%20log%20id:%20c1439726bf1dc5c596b4921c
Thanks!
------------
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 by reproducing the keybase rekey status and keybase rekey paper commands on a new device, using the reported private/soulware TLF and log ID as context. Inspect the rekey flow and logs to determine why the paper key has no effect; done means the TLF is rekeyed and no longer appears in status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100