keybase / keybase/keybase-issues
Can not encrypt: Error: no encryption key found
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Uploaded public and private key generated from GPG. Encryption and decryption work in GPG, but when I attempt to encrypt a message to myself from the website, or from the CLI I get an error.
Website:
From the CLI:
chris@shockwaver:~ $ keybase encrypt -m "Test" shockwaver
error: `gpg` exited with code 2
warn: gpg: D4E0178CFE5DE8C0FEC8869BD266272D6A3C1F3D: skipped: unusable public key
warn: gpg: [stdin]: encryption failed: unusable public key
It's entirely possible that I've messed something up when creating the keybase.io account - but I can't see what.
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
Reproduce the failure using the website and the keybase encrypt CLI command with the uploaded GPG key. Start by investigating the reported gpg output about an unusable public key; done means encryption to the user's own account succeeds through both interfaces.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100