keybase / keybase/keybase-issues
First decrypt threw a weird error message:
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
The very first time I tried to decrypt a file, it threw a GPG error. Subsequent decrypts all go swimmingly. Is there an assumption that the tmp_keyrings dir exists perhaps?
AndrewHs-MacBook-Pro:buildbox andrewhumphrey$ keybase decrypt b
warn: When checking humpy: GpgError: exit code 2
warn: Likely this is a bug or transient error; but the server could be compromised
info: Creating temporary keyring dir: /Users/andrewhumphrey/.cache/keybase/tmp_keyrings
....
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 first-time keybase decrypt b flow and inspect the temporary keyring setup mentioned in the report, especially ~/.cache/keybase/tmp_keyrings. Trace why the initial GPG check runs before that directory is created. Done means the first decrypt completes without the misleading GPG warning or error.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100