keybase / keybase/client

Wrong "No matching keys found" on export

Open
#16,473 26 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
PR merge metrics
PR metrics pending

Description

On a new computer (`nexy`), I tried to import my main GPG key like that:

```
❯ keybase pgp export -q 04460cd228df9e0d42f07643992eb6fafd4e6361 --secret
▶ ERROR No matching keys found
```

As you can see, it does not work. But I can still download the private key from the keybase.io app and import it manually. It makes no sense to me, what is the issue?

Plus, it seems I still can't use it directly, for exemple for passwordstore:

```
❯ pass path/to/auth
gpg: decryption failed: No secret key
```

But the needed key is here:

```
sec rsa4096 2019-03-06 [SC]
04460CD228DF9E0D42F07643992EB6FAFD4E6361
uid [ unknown] Sullivan Senechal
uid [ unknown] Sullivan Senechal
ssb rsa2048 2019-03-06 [E] [expires: 2027-03-04]
ssb rsa2048 2019-03-06 [SA] [expires: 2027-03-04]
```

FYI: All works for the other key.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing `keybase pgp export -q 04460cd228DF9E0D42F07643992EB6FAFD4E636 --secret` with the key details shown in the report, then compare the result with the working key and with `gpg` decryption through passwordstore. Done means the export no longer incorrectly reports no matching keys and the exported secret key can decrypt the reported passwordstore entry.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.