keybase / keybase/client

Other people are seeing failed proofs, but I don't see them.

Open
#14,040 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

On my end (and publicly on the website):

screen shot 2018-10-02 at 14 39 23
screen shot 2018-10-02 at 14 39 34

and on their end:

screen shot 2018-10-02 at 2 39 57 pm screen shot 2018-10-02 at 2 39 57 pm
keybase id smcquay                                                                                                                                                            
▶ INFO Identifying smcquay
✔ public key fingerprint: 15A9 F2D3 0626 B50B D74F B22D BB74 BBB7 45A3 6371
✔ admin of mcquay.me via HTTPS: https://mcquay.me/keybase.txt [cached 2018-10-02 14:35:54 PDT]
✔ "smcquay" on reddit: https://www.reddit.com/r/KeybaseProofs/comments/8tupat/my_keybase_proof_redditsmcquay_keybasesmcquay/ [cached 2018-10-02 10:27:11 PDT]
✔ "smmcquay" on facebook: https://www.facebook.com/smmcquay/posts/1760625604018676 [cached 2018-10-02 10:27:11 PDT]
✔ admin of DNS zone mcquay.me: found TXT entry keybase-site-verification=YdV_lVsKbGLtci7V5SRSahy83cJT8pPhizZI-WdamQU [cached 2018-10-02 14:35:54 PDT]
✔ "smcquay" on github: https://gist.github.com/083515b57e5a0b9b61a1eba573165415 [cached 2018-10-02 10:27:11 PDT]
✔ "smcquay" on twitter: https://twitter.com/smcquay/status/1022370356416274432 [cached 2018-10-02 10:27:11 PDT]

keybase verify seems to hang indefinitely.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported behavior with keybase id smcquay and keybase verify, comparing the reporter's output with the screenshots showing failed proofs. Trace the verification path from these commands and determine why proof failures are not visible locally or why keybase verify hangs. Done means failures are reported consistently and verification completes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.