Rekey request persist for peer who had reset profile but never succeeds
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.44-20180223192708+9a9ccec79
Keybase keeps telling me that I need to take action (rekey) to prevent KBFS data loss between me and
one of my peers, yet the problem is that the peer had reset their profile and the rekey wouldn't succeed. The folder in question won't show up in KBFS, and I can't open up a chat window with that peer as well (error unboxing chat message: EOF).
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 does not identify any files, tests, or entry points. Start by tracing the rekey request for a peer whose profile was reset, then investigate the related KBFS folder and chat errors; done means the repeated rekey request no longer persists and the affected peer data can be accessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100