I just noticed that I do have a bunch of key files in ~/.gnupg/private-keys-v1.d, even though gpg -K does not show them.
Ahah, gpg -K -v shows them... it seems to think they are all expired. It lists the expiration date on my current key as 2018-1-6. I believe that was the *original* expiration date, but then I extended it. gpg 2.1 seems to be failing to recognize the extension. On 6/21/2018 11:27 AM, Phillip Susi wrote: > Ok, so if I checkout and build 2.0.31, remove ~/.gnupg, and import my > keyring, all of my private keys show up. If I check out and build 2.1.1 > and run /usr/local/bin/gpg -K, it upgrades to the new key format and > throws out my private keys: > > gpg: starting migration from earlier GnuPG versions > gpg: porting secret keys from '/home/psusi/.gnupg/secring.gpg' to gpg-agent > gpg: key A70FB705: secret key imported > gpg: migration succeeded > /home/psusi/.gnupg/pubring.gpg > ------------------------------ > sec# rsa2048/A70FB705 2011-12-13 > uid [ unknown] Phillip Susi <[email protected]> > uid [ unknown] Phillip Susi <[email protected]> > > Any suggestions on how to further debug this?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
