client: Wrong "No matching keys found" on export

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 <soullivaneuh@gmail.com>
uid           [ unknown] Sullivan Senechal <sullivan.senechal@gmail.com>
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.

About this issue

Original URL
State: open
Created 5 years ago
Comments: 26 (13 by maintainers)

Most upvoted comments

(…also as @zapu says, there is a bug that we’ve recently fixed…)

maxtaco on May 31, 2019

could also be a local pinentry/gpg misconfigure

i hate to ask for this @mattouille, but will do so anyway. please have some sympathy for us, gpg is basically impossible to support, given it breaks with every minor version and that every combination of platform, package manager and dotfiles provides additional bugs and misconfigurations, and demands further workarounds.

maxtaco on May 31, 2019

That seems similar to a bug in pgp decrypt that we have fixed previously. I’ll take a look, thank you.

zapu on May 31, 2019