keybase / keybase/client

keybase login fails although gpg and private key are installed

Open
#6,923 31 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

When I try to login I get the follwoing Error and advice:

ERROR in Login

Sorry, your account is already established with a PGP public key, but this
utility cannot access the corresponding private key. You need to prove
you're you. We suggest one of the following:

  - install GPG and put your PGP private key on this machine and try again
  - reset your account and start fresh: https://keybase.io/#account-reset

I have gpg installed and the private key to my keybase.io key is also available in my local keychain.
Is there any way to debug how you try to call gpg and what gpgs error message is?

gpg --list-secret-keys --fingerprint  dirkjaeckel
gpg: Note: signatures using the MD5 algorithm are rejected
sec   4096R/A53E4591 2015-04-01 [expires: 2018-02-03]
      Key fingerprint = 1C66 76AF 8572 DDE3 623B  7880 A258 970F A53E 4591
uid                  Dirk Jäckel <dirk@jaeckel.com>
uid                  Dirk Jäckel <dirkjaeckel@keybase.io>
ssb   4096R/BE3132A7 2015-04-01 [expires: 2018-02-03]

my log id: 24473b09e780b96c2f43761c

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

No source files or tests are identified in the issue. Start at the login flow and use log id 24473b09e780b96c2f43761c to inspect how the client invokes GPG and captures its errors; done means identifying why the available private key is rejected and confirming a successful login or a useful diagnostic.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, 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.