keybase / keybase/client

Can't log in -- signing_kid not found

Open
#24,562 6 comments 14 reactions 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

Probably a duplicate of https://github.com/keybase/client/issues/24459 based on error message, but since I have a log, and that's reported on iOS, I'll leave this as a separate bug for now.

  1. keybase login (note: can reproduce on GUI too)
  2. Enter keybase site username
  3. Enter keybase site password
  4. Select 'sign installation' (not import key)
  5. Enter a new name for this device
  6. Enter key password
  7. I get an error: "ERROR signing_kid XXXXXXXXXX not found"

I have previously been able to use the keybase client but it was 2+ years ago. I can log into the website fine. The key it wants to sign with is still present and valid. I do not have any desktop keyrings (I don't have a desktop) and my GPG settings are basically no-cache (prompt for PIN every time).

my log id: a8a0191bb9e8d9a7e053ad1c

P.S. Step 3 (enter keybase site password) is WAY too aggressive about capturing keystrokes and input. I can't switch screens with my usual awesomewm shortcuts or focus another window by clicking the mouse while it's up.

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 with the keybase login signing-installation flow and compare the reported error with issue 24459, including the provided log id if available. Reproduce the failure after selecting “sign installation” and determine what should happen when the signing key is present; done means login completes without the signing_kid not found error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.