keybase / keybase/keybase-issues
Tweet-sized hash is 7 signs shorter than what I get via cli
Open
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
In order to examine a Twitter proof I am using the following command line
`gpg --dearmor $ gpg --dearmor
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the reported result using the Twitter proof's “Their signed statement” and the shown gpg, openssl, and base64 pipeline. Compare that output with the tweet-sized hash for the linked Keybase profile, then document why they differ and provide a command that produces the identical tweet-sized value.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100