boxing error: unable to get crypt keys: Error unboxing teamEK@generation:615 missing use rEK@generation:1509
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
About once per day my keybase server fails and begins to report this message when attempting to send a message "boxing error: unable to get crypt keys: Error unboxing teamEK@generation:615 missing use
rEK@generation:1509"
Simply restarting does not always solve the issue, often I have to restore a backup of my keybase profile (~/.config/keybase, ~/.local/share/keybase)
my log id: 54ad0e7eba75b6971c53501c
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reported log entry and the Keybase profile locations (~/.config/keybase and ~/.local/share/keybase); no source file, test, or entry point is named. Reproduce the recurring boxing and unboxing failure, identify its cause, and verify that messaging no longer reports the missing key error after recovery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100