Hello, Thank you for your report. I think I located the issue of migration.
Phillip Susi <[email protected]> wrote: > 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. For the problem of importing secring.gpg directly, we have a task: https://dev.gnupg.org/T3101 Basically, secring.gpg only has the information of expiration when it's created. After changing expiration, it is only recorded in pubring.gpg. So, it is recommended to do somthing like: $ gpg --homedir ~/.gnupg.old --export-secret-keys | \ gpg --homedir ~/.gnupg --import (instead of doing --import ~/.gnupg/secring.gpg directly.) However, in gnupg/g10/migrate.c, GnuPG itself does that (!). This should be fixed. -- _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
