keybase / keybase/keybase-issues

can't prove via twitter

Open
#1,284 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

maybe the fault is in my side, I can't know. the error at the end is display in red. I just need a meaningful message, or know where get info about the error 1002

```
$ keybase prove twitter sniffjoke
info: Updated file: /home/qq/.cache/keybase/session.json

You need a passphrase to unlock the secret key for
user: "vecna (a Random GlobaLeks Developer) "
1024-bit DSA key, ID B842093DC6765430, created 2009-08-25

error: bad signature: Expected a signature on the payload message (error #1002)
$
```

Thanks!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `keybase prove twitter sniffjoke` and inspect the reported error 1002, especially the `bad signature` message. Determine what information is available for diagnosing the failed Twitter proof and document a meaningful user-facing error or a clear way to find more details. No source file or test is identified in the issue.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.