Peculiar behavior of --list-secret-keys
Robert J. Hansen
rjh at sixdemonbag.org
Mon Jul 20 19:01:15 CEST 2015
My newly-generated secret key is demonstrating some "first it's there,
then it's not" behavior. Behold, it's there:
[rjh at localhost ~]$ gpg --list-secret-key b44427c7
sec 3072R/1DCBDC01B44427C7 2015-07-16
uid Robert J. Hansen <rob at enigmail.net>
uid Robert J. Hansen <rjh at sixdemonbag.org>
ssb 3072R/DC0F82625FA6AADE 2015-07-16
Behold, it's not:
[rjh at localhost ~]$ gpg2 --list-secret-keys
/home/rjh/.gnupg/pubring.kbx
----------------------------
sec rsa2048/B700F482FEAF8109 2005-02-22 [revoked: 2009-03-17]
uid [ revoked] Robert J. Hansen
uid [ revoked] Robert J. Hansen <rjh at sixdemonbag.org>
sec dsa2048/23806BE5D6B98E10 2008-07-30
uid [ unknown] Robert J. Hansen <rob at enigmail.net>
uid [ unknown] Robert J. Hansen <rjh at sixdemonbag.org>
uid [ unknown] Robert J. Hansen <rob at mozilla-enigmail.org>
uid [ unknown] Robert J. Hansen <rjh at secret-alchemy.com>
uid [ unknown] [jpeg image of size 14285]
ssb elg2048/B8A6B74C001892C2 2008-07-30
ssb rsa2048/446A446F810DB5D0 2013-03-14
Also, GnuPG seems to have lost track of the fact that D6B98E10 is an
ultimately-trusted key.
More information about the Gnupg-users
mailing list