[Bug 1565963] Re: gpg secret keys not migrated after upgrade to gnupg 2.1

[Carlo Wood]

Hi, I have the same problem; I upgraded from ubuntu 16.04 to 18.04 (one
LTS release to the next). To my astonishment afterwards I couldn't get
into my bank accounts anymore because I can't decrypt my files!

The output of the original conversion is:

>gpg --decrypt digid.nl.gpg
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/home/carlo/.gnupg/secring.gpg' to gpg-agent
gpg: key 29BD5E6C7C8DEF37: secret key imported
gpg: key 3232F9CFE80A9EC5: secret key imported
gpg: key 027353B08370CB05: secret key imported
gpg: migration succeeded
gpg: encrypted with RSA key, ID 6FD2C61D624ACAD5
gpg: decryption failed: No secret key

After that I tried running:

>gpg --import < /home/carlo/.gnupg/secring.gpg
gpg: key 29BD5E6C7C8DEF37: "TXXXXX3" not changed
gpg: key 29BD5E6C7C8DEF37: secret key imported
gpg: key 3232F9CFE80A9EC5: "AXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXl at gmail.com>" not changed
gpg: key 3232F9CFE80A9EC5: secret key imported
gpg: key 027353B08370CB05: "Carlo (XXXXXX) <carlo at alinoe.com>" not changed
gpg: key 027353B08370CB05: secret key imported
gpg: Total number processed: 5
gpg:     skipped PGP-2 keys: 2
gpg:              unchanged: 3
gpg:       secret keys read: 3
gpg:  secret keys unchanged: 3

Note the 'skipped PGP-2 keys: 2' ?!

What, why? How do I get those back?!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/1565963

Title:
  gpg secret keys not migrated after upgrade to gnupg 2.1

Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to gnupg 2.1 I can no longer see my keys in seahorse
  (Passwords and Keys in apps scope in unity) and evolution cannot find
  my gpg keys. Someone said this might be related to
  https://www.gnupg.org/faq/whats-new-in-2.1.html#autostart and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796931

  Reading the Debian bug I see someone mentioned that running this might help:
  $ gpg2 --import < ./.gnupg/secring.gpg

  I did that and gpg2 went through each of my private keys to import
  them. When done I logged out and back in and seahorse saw my keys. I'm
  not sure why gpg2 didn't prompt me before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1565963/+subscriptions