keybase / keybase/keybase-issues

Problems verifying a signed message

Open
#468 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

A friend of mine, Keybase username [arcticlight](https://keybase.io/arcticlight), sent me a signed, encrypted message generated by Keybase's web interface. When I attempt to decrypt this message, I get an error saying `Error: Cannot verify username, no self-signed proofs given`. My friend does have what appear to be valid Twitter and GitHub proofs on their Keybase profile. When my friend sends me an unsigned encrypted message, everything works fine.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the signed, encrypted message flow from Keybase's web interface and compare it with the unsigned encrypted case. Trace the `Cannot verify username, no self-signed proofs given` error and the friend's Twitter and GitHub proofs; done means identifying why the signed message fails verification and confirming successful decryption.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.