keybase / keybase/client

Trouble signing in to client

Open
#4,083 2 comments 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 am having trouble signing in to keybase in the linux client. Whenever I try it either in the GUI or with "keybase login" on the CLI I can enter my username and password without issues, it then asks me to name the device and the gives me this error (copied from the commandline but other than formatting it's the same in the GUI):

▶ ERROR openpgp: invalid argument: no valid signing keys

I tried first with this package: https://www.archlinux.org/packages/community/x86_64/keybase/

But am on this package now:
https://aur.archlinux.org/packages/keybase-bin/

Have had it running before but it was (very) long ago removing ~/.config/keybase did not help (i have restored it now).

My keys recently expired so I have been editing it (updating the expiration date) I also uploaded the new public key using the keybase.io website and bash + curl (the fingerprint is the same).

I mostly use my keys for email and my client handles it automatically, so I might very well have done something wrong in gpg but I can't figure out what.

I sent a log with "keybase log send", I hope that will give you more details, if more is needed I'm happy to help.

my log id: 9e437c8e5963bc2cbba5351c

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

Reproduce the failure with keybase login on Linux using the reported renewed-key setup, then inspect the submitted log with ID 9e437c8e5963bc2cbba5351c and the OpenPGP signing-key error. Done means sign-in succeeds through both the CLI and GUI without the invalid-signing-key error.

Written by the indexing model from the issue text.

Assessment

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