keybase / keybase/keybase-issues
User listed as having no key although key is present
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Apologies if this one has been posted elsewhere. This user is listed as a mystery user with no key, even though a public key is present, as is evident from the page itself as one can "Encrypt" and "Verify".
This seems to happen because the user uploaded their public key without signing the keybase blob with their private key.
As an aside, relating also to #1375, I was wondering if the latter check would not be made a lot easier on the user by simply sending an encrypted (and sufficiently complicated) verification link to their claimed email address.
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 mystery-user behavior on the linked Keybase profile and compare the public-key display with the signed keybase blob handling described here. Read the related discussion in #1375 before tracing the profile's Encrypt and Verify behavior. Done means a present public key is handled consistently even when the blob is unsigned, with verification behavior covered.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100