gpg2 2.1.5 exports non existing private keys

[Daniel Kahn Gillmor]

Hi Meno--

On Fri 2016-10-07 10:07:24 -0400, Meno Abels wrote:

> i have on my system no private keys and 2.0.30_2 does this:
>
> /usr/local/Cellar/gnupg2/2.0.30_2/bin/gpg2 --export-secret-keys -a xxxxxBEEF
> gpg: WARNING: nothing exported

how do you know that you have no private keys?  do you have anything in
~/.gnupg/private-keys-v1.d/ ?

> if i do this with 2.1.15 i get:
>
> -----BEGIN PGP PRIVATE KEY BLOCK-----
> Comment: GPGTools - http://gpgtools.org
>
> lDsEV02MJBYJKwYBBAHaRw8BAQdAHBS1e25+m5QZw7zU0giU6pNotiW7wj2boJzg
> 5bAKXV//…..
> ….
>
> is this the right behaviour?

versions of GnuPG before 2.1 kept their OpenPGP secret key material in
~/.gnupg/secring.gpg.  since 2.1, secret key material is stored in the
gpg-agent itself, which by default will manage them in
~/.gnupg/private-keys-v1.d/.

hth,

        --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 930 bytes
Desc: not available
URL: </pipermail/attachments/20161007/6b8431ba/attachment.sig>