gpg 2.1.6 toggle doesn't

[Marko Božiković]

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

On 27/07/2015 10:14, Kristian Fiskerstrand wrote:
> On 07/27/2015 11:03 AM, Kristian Fiskerstrand wrote:
>> On 07/27/2015 10:48 AM, Marko Božiković wrote:
>>> On 25/07/2015 13:26, MFPA wrote:
>>>> Hi
> 
> 
>> ..
> 
>>> Ok, but why doesn't it make much sense anymore? Is there another way
>>> to get private key info while in --edit-key mode? (e.g. key location,
>>> like the bug submitter mentions)
> 
> 
>> 1.4 and 2.0 have separate keyrings for public keys (pubring.gpg) and
>> private keys (secring.gpg). In 2.1 everything is handled in agent and
>> keys stored in platform agnostic format on per-key basis based on
>> keygrip. I.e. there is no more toggling between keyrings.
> 
> 
> 
> Was a bit quick there, so to clarify that a bit, all secret-key 
> operations are handled in the agent, and based on keygrip calculated in
> the single-store public keyring.

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?)


- -- 
Marko
-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJVtgvqAAoJEE8XQV0qn4Bv4dEIAKSOxfmrbgXZHK+0lzYMgSeB
5Mm3MWHBKx7mq6ffMm/MBsCoxjjLGf/boTTrG0t0DYjhKw0svZjEAkYegSYI5wqG
nt53+RtUTIbhcoSn1Fca+zoR5ppzTHMu+cKA1r2E6H/UgBovTcu+dpCa6he0Lqef
VQIf5ESJUi53Av9Wphjozt/RE2MSueijMG067fRyy8pfrw63nPvoo0u3toxxO0r1
mzwLKdVeM+3O1mhtJOzBrB4YWPoFT6kzvjHLGyxiMlcjTPQMCfW0jH5h6j65FFa9
m+f+s7f0x7FbXWpQAl/IjIfgpiL5mHCh0jAWvZWQxCS6dbe0lR7CB58PIgmBAE0=
=rgVw
-----END PGP SIGNATURE-----