gpg 2.1.6 toggle doesn't

[MFPA]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi


On Monday 27 July 2015 at 3:06:53 PM, in
<mid:55B63AFD.4030702 at kset.org>, Marko Božikovic wrote:



> On 27/07/2015 14:31, MFPA wrote:
>> When I run gpg -K, or gpg --list-secret-keys, the
>> listing for each key  starts with the location of
>> pubring.kbx and not the location of
>> private-keys-v1.d.

> Hi,

> I'm not sure we're talking about the same thing...

I think we are but I am not understanding something correctly.



> When I run gpg -K (2.1), I get a listing of my private
> keys' info from my pubring.kbx.

I thought the private keys were in private-keys-v1.d, not in pubring.kbx.




> In the listing, there
> are indicators for missing/deleted private keys (sec#)
> and private key "placeholders" (not sure if that's the
> term) for keys that are stored on the card (ssb>).

I get the "#" for revoked, missing or deleted private keys, buy I
don't have any cards so don't see ">" in my listing.



> This is what the output looks like (notice # and >'s)


> sec#  rsa4096/AAAAAAAA 2015-05-11 [expires: 2018-05-10]
> uid       [ultimate] <UID 1>
> uid       [ultimate] <UID 2>
> ...
>ssb>  rsa2048/XXXXXXXX 2015-05-11 [expires: 2016-05-10]
>ssb>  rsa2048/YYYYYYYY 2015-05-11 [expires: 2016-05-10]
>ssb>  rsa2048/ZZZZZZZZ 2015-05-11 [expires: 2016-05-10]


I get something like:-


Keyring: C:/PATH/TO/pubring.kbx
- -----------------------------------------------------------------------------------
sec   rsa2048/0xAAAAAAAAAAAAAAAA 2014-11-09
      Key fingerprint = AAAA AAAA AAAA AAAA AAAA AAAA AAAA AAAA AAAA AAAA
      Keygrip = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
uid                 [ultimate] <UID 1>
ssb   rsa2048/0xXXXXXXXXXXXXXXXX 2014-11-09
      Keygrip = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
ssb#  nistp256/0xYYYYYYYYYYYYYYYY 2014-11-09 nistp256 [revoked: 2015-01-16]
      Keygrip = YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY



My point was that when I list the public keys, the listing for each
key starts with "Keyring: C:/PATH/TO/pubring.kbx". When listing the
private keys, I would expect to instead be given the path to
private-keys-v1.d.



> Previously, using toggle, you could see that info while
> running gpg --edit-key

Yes, indeed. But not any more.


- --
Best regards

MFPA                  <mailto:2014-667rhzu3dc-lists-groups at riseup.net>

Dreams come true on this side of the Rainbow too!
-----BEGIN PGP SIGNATURE-----

iQF8BAEBCgBmBQJVt9RqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwekQIAJxyJcgdOA/24sUF9Vd52jND
1cDLJhVwr1Py7my2C0HF8cYyOGFcVsyBsiozcrzijf6rbLuLAr2P6lj/a+nWgIjf
KIe+FWE7A2HtMe4tblvfDZAOYRhdsrlDrP5vgxfy9T/Ak6GDWrKnsUtZSPzgdm+c
/u67ZsQjSYY8uaic/lhO7y4eVjNqc1ykeBEtvb5Inv8KINGh+l9nUUelGJIz7ufv
Kf1V6jrfRCrzGdx0lqUFYZQrUN1AahEK4hXp5SXcn656waUII3bi+S6OEJOWQxu/
U1JGY06IsH/+N1tbXxBBBIMT7GeS/sfYogyVBAyNU9TqRUU6dUyb6dgbW4dLD8WI
vgQBFgoAZgUCVbfUc18UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45MciAQCr6aQenSx7l4cTed9uXH8+fx8z
nF+wBxQSm0tyTqSrRwD+I4eY7tcukQZS4zaMFVY36Q9/Z4xZj8GD/oxWQWC1mwc=
=ehOP
-----END PGP SIGNATURE-----