-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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. - -- - ---------------------------- Kristian Fiskerstrand Blog: http://blog.sumptuouscapital.com Twitter: @krifisk - ---------------------------- Public OpenPGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 - ---------------------------- Aquila non capit muscas The eagle does not hunt flies -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJVtfZ6AAoJECULev7WN52F/ucH/0TiasUsLalQsJsgjTuSG3Ee ZBX90BOZOoxGvitIuLqY61+78Bwz0nSZe91Ar+UTPxZM+PnJIkL/tFwobJ5r6Oci fopEU8OZzWxSafLlPEr4CZkzy9lOqfra+jFyYnNXPVsbR/hQhFyi5bfnRA1gy0Jg NEEhUbWVHBt/V4ee79pVJMd9X5mRDDnknuQPLEvr8TdAYf+nK0AUKl0vHAF9JzCq bMIywD0RzzdVALucuWknu/qJIqS4VEA3ON1Y3Ipx52+PSqAo4LkHY9BDUmQuRUd5 GV6024G3e5Laj4PVz8eulKlMUIGInJX9CvJxDxggFWSZpnTpT+XlOdtWnVO1fr0= =ZaSY -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
