Daniel Kahn Gillmor <[email protected]> writes: > ok, so the keygrip for 0x7CE29A76E9769486 is > FD1DA474D3DF3C728C54F9E479EDFC5BBE2E14EA
> (via "gpg2 --with-keygrip --list-keys 7CE29A76E9769486") > do you see > ~/.gnupg/private-keys-v1.d/FD1DA474D3DF3C728C54F9E479EDFC5BBE2E14EA.key > ? No, that file doesn't exist. So it looks like you've located the problem. > I agree with you that this key clearly has valid self-sigs. it does in > my copy as well. > can you show the same output from gpg2 as well as gpg ? I can't, no, because I get the same problem: mithrandir:~$ gpg2 -kv D15D313882004173 gpg: using classic trust model gpg: keydb_get_keyblock failed: Legacy key gpg: error reading key: No public key Aha. Okay, I seem to have fixed it, although I still don't really understand what happened. On a hunch, I ran: $ gpg2 --import ~/.gnupg/pubring.gpg That spat out a bunch of output (tons and tons of those legacy key messages), and then I ran: $ gpg2 --import ~/.gnupg/secring.gpg again. That prompted me for the passphrase for the private key for D15D313882004173, and then apparently successfully imported it. Now, the gpg2 command works: mithrandir:~$ gpg2 -kv D15D313882004173 gpg: using classic trust model pub rsa4096/D15D313882004173 2009-05-29 [expires: 2017-09-17] uid [ultimate] Russ Allbery <[email protected]> uid [ultimate] Russ Allbery <[email protected]> uid [ultimate] Russ Allbery <[email protected]> uid [ revoked] Russ Allbery <[email protected]> uid [ultimate] Russ Allbery <[email protected]> sub rsa4096/7CE29A76E9769486 2009-05-29 [expires: 2017-09-17] sub rsa2048/7D80315C5736DE75 2010-09-17 [expires: 2016-03-20] and now assword works again. So, something weird about the automated key import process for gpg2? -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
