gpg 2.1.6 toggle doesn't
Marko Božiković
bozho at kset.org
Mon Jul 27 16:06:53 CEST 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 27/07/2015 14:31, MFPA wrote:
> Hi
>
>
> On Monday 27 July 2015 at 11:46:09 AM, in
> <mid:55B60BF1.3040900 at kset.org>, Marko Božikovic wrote:
>
>
>> I know that, and I'm using 2.1 exclusively... Still, it would be nice
>> to be able to see the state of private keys (e.g. primary key not
>> present in the keyring, private keys are on the card, etc) while
>> editing keys. It seems that the only way to see private key info is
>> running gpg(2) -K (or am I missing something?)
>
> 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...
When I run gpg -K (2.1), I get a listing of my private keys' info from my
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>).
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]
Previously, using toggle, you could see that info while running gpg --edit-key
Cheers,
- --
Marko
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJVtjr4AAoJEE8XQV0qn4BvSGEH/25G8HLCdrVmXgs9YRXfpWqp
Y62qTVfj/4YSpm0MHcQAn07f0GUoJparduX2Lh/hAd92ujb6Slg73AJWewza1oqd
m59J4+KWN22oFOBqaqBTK1eYXmSLSj9U9DwDXVxAvancGodME2krwsyLHgHUTeVU
yDaqoe+GK+eaX+K7v4yJ99rK8yUC26CGCcjj5Ygy0dAYIpYLNVS+8ATfaCgxlLx2
/0/DiaGog4cKWol3pJm2881RFyyE9JhgepzW+4cXuKBx0lDSJxt5DUg67VK2yJpX
XVmM1IrkKMXZkxoBQDulRrRh73YwJ5pY124sad9bzz714uAWKhiEBa+Z+YUf6mk=
=k8ug
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list