keybase / keybase/client

"keybase login" fails with eldest called on user with existing eldest KID

Open
#2,991 1 comment 0 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

I used to use the node client but am now running from brew install keybase. I can't login to do anything though.

$ keybase login
Your keybase username or email address: _____
▶ ERROR eldest called on user with existing eldest KID

$ gpg --version
gpg (GnuPG) 2.1.12
libgcrypt 1.7.0
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

my log id: fd5603d554461e688fd3901c

My key is on a yubikey, but I've also tried on the system that has the master key on disk and it gives the same error. I think something is maybe wrong with my account since the comment on this part of the code says "this shouldn't happen, but make sure"

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

The report identifies keybase login as the entry point and includes the eldest called on user with existing eldest KID error, GnuPG 2.1.12 details, and log id fd5603d554461e688fd3901c. Start by reproducing the login failure and tracing the code referenced by the report's comment; done means login succeeds with the existing account and key, including the YubiKey setup.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.