keybase / keybase/keybase-issues
If uploading key without encryption, then cannot use Keybase web to encrypt message
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I generated a key that is signing only using gpg --gen-key, and then imported the public key onto keybase using keybase select --multi --import-only
However, now when I try send an encrypted message to myself using the web interface, it fails because the presence of the signing only key. Shouldn't the correct behavior to skip this key? As it stands, there's a big trade-off of not publishing these signing only keys vs. having broken easy encrypt feature.
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 reported flow with a signing-only key generated by gpg --gen-key, imported through keybase select --multi --import-only, then use the web interface to encrypt a message. Done means the signing-only key is skipped and encryption to the user succeeds.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100