keybase / keybase/client

command line keybase can't update key

Open
#7,528 5 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 tried to update my pgp key on the website. It said I need to use the command line app to do it. However, it does not work, claiming that no keys match the given key IDs. This seems related to https://github.com/keybase/client/issues/4817 and #5788.

$ keybase pgp update
▶ ERROR Login required
bminton.is-a-geek.net:~$ keybase login
Your keybase username or email address: brian@minton.name
▶ WARNING Skipping expired primary key 4E1D D7E4 475D DF9F BACA 8E19 7AFD 668F 50F3 F076
▶ WARNING Skipping expired primary key AB94 E395 78CE 0967 2542 A7B3 178C 3E66 E177 AFF0
In order to authorize this installation, keybase needs to sign this installation
with your GPG secret key 0424DC19B678A1A9.

You have two options.

(1) Keybase can use GPG commands to sign the installation.

(2) Keybase can export your secret key from GPG and save it to keybase's local encrypted
keyring. This way, it can be used in 'keybase pgp sign' and 'keybase pgp decrypt'
going forward.
Which do you prefer?: ▶ WARNING Skipping expired primary key BC37 88BA 148C CF84 03BB C160 7F41 3723 1901 AD94
1


  • Final step: name your new device! *

Enter a public name for this device: laptop
▶ ERROR bad signature: Can't find a key for 6b8eb3a065cfbaa9: No keys match the given key IDs (error 1002)

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 by reproducing the command-line flow with keybase pgp update and keybase login, including the expired-key warnings and bad-signature error. Compare the behavior with related issues #4817 and #5788; done means the command can update the user's PGP key without the “No keys match the given key IDs” failure.

Written by the indexing model from the issue text.

Assessment

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