Won't recognize my secret key
gniibe at fsij.org
Fri Jun 22 04:41:38 CEST 2018
Thank you for your report. I think I located the issue of migration.
Phillip Susi <psusi at ubuntu.com> 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:
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.
More information about the Gnupg-users