On Donnerstag, 21. Juni 2018 17:27:05 CEST 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 <ps...@ubuntu.com>
> uid [ unknown] Phillip Susi <ps...@cfl.rr.com>
>
> Any suggestions on how to further debug this?
I have imported your key 015F4DD4A70FB705 (btw, you should really enable
"keyid-format long" in your gpg.conf because there are two keys with short key
ID A70FB705 and uid "Phillip Susi <ps...@ubuntu.com>").
$ gpg --list-keys --verbose 015F4DD4A70FB705
gpg: using classic trust model
gpg: Note: signature key 9AC13A54FA9EEEF9 expired Fr 13 Dez 2013 06:00:00 CET
gpg: Note: signature key 8E45A0223348AAF0 expired Mi 26 Nov 2014 05:28:21 CET
gpg: Note: signature key D455AF0D9C8E5E51 expired Do 29 Okt 2015 02:29:24 CET
gpg: Note: signature key 107951615CBBA516 expired Fr 30 Sep 2016 00:11:23 CEST
pub rsa2048/015F4DD4A70FB705 2011-12-13 [SCA]
1B49F933916A37A3F45A1812015F4DD4A70FB705
uid [ unknown] Phillip Susi <ps...@ubuntu.com>
uid [ unknown] Phillip Susi <ps...@cfl.rr.com>
sub rsa2048/D1FDDE0451FEF1C9 2011-12-13 [E] [expired: 2013-12-13]
sub rsa2048/9AC13A54FA9EEEF9 2011-12-14 [S] [expired: 2013-12-13]
sub rsa2048/8E45A0223348AAF0 2013-11-26 [S] [expired: 2014-11-26]
sub rsa2048/1B6CD765BDCC7F92 2013-11-26 [E] [expired: 2014-11-26]
sub rsa2048/D455AF0D9C8E5E51 2014-10-29 [S] [expired: 2015-10-29]
sub rsa2048/BF0C615393A02CCD 2014-10-29 [E] [expired: 2015-10-29]
sub rsa2048/107951615CBBA516 2015-10-05 [S] [expired: 2016-09-29]
sub rsa2048/EBD87E9510850B71 2015-10-05 [E] [expired: 2016-09-29]
sub rsa2048/DB2EC3B96100FE84 2017-01-06 [S] [expires: 2019-01-06]
sub rsa2048/0E33D4FE0F60068B 2017-01-06 [E] [expires: 2019-01-06]
That's with
$ gpg --version
gpg (GnuPG) 2.2.7
libgcrypt 1.8.2
So, with respect to your public key everything looks good. Are you sure you
are trying to migrate the most recent version of your key? Which expiration
dates does the "working system" list? Try importing your public key from a
keyserver.
Regards,
Ingo
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
