keybase / keybase/keybase-issues

Unable to login to keybase using a Yubikey

Open
#3,067 5 comments 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

Hi,
I registered an account today and everything worked fine, registering my public key (using the shell/curl method).

However, when I downloaded the Keybase client on my Mac I am unable to login. The first error message I received was:

```
Your keybase username or email address: hedlund
▶ NOTICE Failed to parse public key at position 0 [tags:LU=******]
▶ ERROR Bad key family: No key found for XXX
```
I read some other issues where bad formatting of the public key could result in something similar, so I exported the key again and reimported it on the Keybase website (again without errors).

Now, every time it try to login I get:

```
Your keybase username or email address: hedlund
▶ NOTICE Failed to parse public key at position 0 [tags:LU=******]
▶ ERROR Sigchain specified that KID XXX is a PGP key with hash YYY but no version of the key with that hash was found
```

This smells awfully similar to: https://www.bountysource.com/issues/30578331-sigchain-specified-that-kid-xxx-is-a-pgp-key-with-hash-yyy-but-no-version-of-the-key-with-that-hash-was-found-error-901

But that issue was marked as fixed a year ago..

keybase version 1.0.33-20171003193446+d9ceb86ac
OS: macOS Sierra, 10.12.3

Any ideas on how to proceed in resolving this? :-)

Best regards,
Henrik

Contributor guide

No contributing guide indexed for this repository

Research direction

Begin with the Keybase client login flow on macOS and compare it with the shell/curl registration path. Reproduce the report using the listed client version and inspect the public-key parsing and sigchain errors, including the related issue linked in the report. Done means a Yubikey-backed account can log in without either error.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
authentication, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.