keybase / keybase/keybase-issues
keybase prove fails with error 1002
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Just installed keybase and pushed my PGP key (https://keybase.io/kravietz). Now, command:
```
keybase -d prove twitter kravietz2
```
fails with the following error:
```
error: bad signature: We don't have a key for the requested PGP ops (error #1002)
```
Here are my keys:
```
$ gpg -K --with-fingerprint --with-colons 07E16AEB648F17ED
sec::1024:1:88CED450C4DD9DCA:1144873541::::::escaESCA::::
fpr:::::::::462E1F1AEF9FBEBCCF62602188CED450C4DD9DCA:
uid:::::1144873542::BF23CA8FD18C55D5E8B3790D599114880DA7AD15::"pawel.krawczyk@hush.com" :
uid:::::1144873541::C6D833D262962A320B779965F7A0773EBE684C7A::keybase.io/kravietz :
ssb::2048:1:07E16AEB648F17ED:1144873542::::::esca::::
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the failure with `keybase -d prove twitter kravietz2` and compare it with the supplied error #1002 and GPG key details. Trace the PGP handling used by the prove command, then verify that the same Twitter proof succeeds with the listed key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cryptography
- Domain
- cryptography
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100