Hi Kevin, * Kevin J. McCarthy <[email protected]> [01. Mar. 2016]: > On Tue, Mar 01, 2016 at 11:45:50PM +0100, Gregor Zattler wrote: >> Dear mutt users, I use mutt on debian stretch with gpgme and >> recently gnupg2 was upgraded to version 2.1 >> >> Now when I want to send an signed and encrypted email mutt is >> configured to >> >> sign as: 0xB557830478789E7B98D7FEABF2EB825AD25307CA >> >> and says so in the send menu. But in the last line of the screen >> it states: >> >> ambiguous specification of secret key >> `0xB557830478789E7B98D7FEABF2EB825AD25307CA'? > > Mutt is seeing more than one result when querying for secret keys > matching that fingerprint. When it gets the second result back from > gpgme, it's aborting with that error. > > What does `gpg2 --list-secret-keys 0xB55....` show?
$ gpg2 --list-secret-keys 0xB557830478789E7B98D7FEABF2EB825AD25307CA gpg: keyserver option 'include-disabled' is unknown gpg: keyserver option 'honor-http-proxy' is unknown gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 0x00000000 occurs more than once in the trustdb gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 0x00000000 occurs more than once in the trustdb gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 0x00000000 occurs more than once in the trustdb gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 0x00000000 occurs more than once in the trustdb gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 0x00000000 occurs more than once in the trustdb Keyring: /home/grfz/.gnupg/pubring.gpg -------------------------------------- sec dsa1024/0xF2EB825AD25307CA 2001-09-29 [SC] uid [ultimate] Gregor Zattler (do not use [email protected] any more) <[email protected]> uid [ultimate] Gregor Zattler <[email protected]> uid [ultimate] Gregor Zattler <[email protected]> uid [ultimate] Gregor Zattler (do not use [email protected] any more) <[email protected]> ssb elg4096/0xAD8A61F5F877E5F0 2001-09-29 [E] Keyring: /home/grfz/.gnupg/import-zu-sortieren-keyring.gpg ---------------------------------------------------------- sec dsa1024/0xF2EB825AD25307CA 2001-09-29 [SC] uid [ultimate] Gregor Zattler (do not use [email protected] any more) <[email protected]> uid [ultimate] Gregor Zattler <[email protected]> uid [ultimate] Gregor Zattler <[email protected]> uid [ultimate] Gregor Zattler (do not use [email protected] any more) <[email protected]> ssb elg4096/0xAD8A61F5F877E5F0 2001-09-29 [E] Urghs! The secret key is in public keyring!? > Also, are you seeing the problem with the classic interface? I'll test this with this email. The classic interface uses gpg version 1.4.20. It's not possible to set the signing key via fingerprint, but when I give the short key id the long key id is shown in the send menu. If this email is signed, then there was no problem with the classic interface. Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.-
signature.asc
Description: PGP signature
