Peculiar behavior of --list-secret-keys

Juan Miguel Navarro Martínez juanmi.3000 at
Mon Jul 20 20:23:39 CEST 2015

You are using GnuPG 1.x and GnuPG 2.1.x, they use different keyring
locations for storing public and secret keys.

The only time when GnuPG 2.1.x uses "pubring.gpg" instead of
"pubring.kbx" is when it detects public keys on pubring.gpg before
installing it.

So now you have GnuPG 1.x using pubring.gpg and secring.gpg and GnuPG
2.1.x using pubring.kbx and private-keys-v1.d folder. Every keys you
import or make in GnuPG 1.x won't appear in GnuPG 2.1.x and vice versa,
you'll have to use --import and --export on both versions to sync the

As to way GnuPG 2.1.x is looking at pubring.kbx, I don't know. I suppose
you made a secret key with GnuPG 2.1?

On 2015/07/20 at 19:02, Robert J. Hansen wrote:
> Also, why is it trying to read secret keys from my public keybox?  See
> below.
>> [rjh at localhost ~]$ gpg2 --list-secret-keys
>> /home/rjh/.gnupg/pubring.kbx
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at

Juan Miguel Navarro Martínez

GPG Keyfingerprint:
5A91 90D4 CF27 9D52 D62A
BC58 88E2 947F 9BC6 B3CF

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20150720/c6bffbfd/attachment.sig>

More information about the Gnupg-users mailing list