GNOME Bugzilla – Bug 655509
Fails to decrypt a GPG encrypted message
Last modified: 2012-02-10 23:43:53 UTC
Hi, today I received a GPG encrypted message that Evolution was unable to decrypt. However, manually decrypting the message on the command line via "gpg -d encrypted.asc" worked. Instead of the decrypted message Evolution showed the following lines in red (without indentation, modified to keep privacy, hhh and iii are my own keys): Could not parse PGP/MIME message gpg: armor header: Version: GnuPG v1.4.11 (GNU/Linux) gpg: armor header: Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ gpg: public key is aaa gpg: public key is bbb gpg: public key is ccc gpg: public key is ddd gpg: public key is eee gpg: public key is fff gpg: public key is ggg gpg: public key is hhh gpg: using subkey hhh instead of primary key iii gpg: using subkey hhh instead of primary key iii gpg: public key is jjj gpg: encrypted with ELG-E key, ID jjj gpg: encrypted with ELG-E key, ID ggg gpg: encrypted with RSA key, ID fff gpg: encrypted with RSA key, ID eee gpg: encrypted with RSA key, ID ddd gpg: encrypted with RSA key, ID ccc gpg: encrypted with ELG-E key, ID bbb gpg: encrypted with ELG-E key, ID aaa gpg: encrypted with 2048-bit ELG-E key, ID hhh, created 2006-05-17 "Fabian Greffrath <fabian@greffrathnojunkpleasexyz.com>" gpg: AES encrypted data gpg: original file name='' gpg: Signature made Thu Jul 28 15:45:24 2011 CEST using DSA key ID kkk gpg: Can't check signature: public key not found The manually decrypted text begins with the following two lines (without indentation): Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am using evolution 3.0.0-2 and evolution-data-server 3.0.0-1 from Debian as well as gnupg 1.4.11-3.
Thanks for a bug report. Maybe try: $ CAMEL_DEBUG=gpg evolution from a command line, whether it shows anything usable. Evolution is passing some arguments to gpg, but mostly is the same as when you run it from console. Could there be an issue with the following? > gpg: Can't check signature: public key not found
(In reply to comment #1) > Thanks for a bug report. Maybe try: > $ CAMEL_DEBUG=gpg evolution It shows the following: $ CAMEL_DEBUG=gpg evolution status: [GNUPG:] ENC_TO aaa 16 0 status: [GNUPG:] ENC_TO bbb 16 0 status: [GNUPG:] ENC_TO ccc 1 0 status: [GNUPG:] ENC_TO ddd 1 0 status: [GNUPG:] ENC_TO eee 1 0 status: [GNUPG:] ENC_TO fff 1 0 status: [GNUPG:] ENC_TO ggg 16 0 status: [GNUPG:] ENC_TO hhh 16 0 status: [GNUPG:] USERID_HINT hhh Fabian Greffrath <fabian@greffrath.com> status: [GNUPG:] NEED_PASSPHRASE hhh iii 16 0 status: [GNUPG:] GOOD_PASSPHRASE status: [GNUPG:] ENC_TO kkk 16 0 status: [GNUPG:] NO_SECKEY kkk status: [GNUPG:] NO_SECKEY ggg status: [GNUPG:] NO_SECKEY fff status: [GNUPG:] NO_SECKEY eee status: [GNUPG:] NO_SECKEY ddd status: [GNUPG:] NO_SECKEY ccc status: [GNUPG:] NO_SECKEY bbb status: [GNUPG:] NO_SECKEY aaa status: [GNUPG:] BEGIN_DECRYPTION status: [GNUPG:] PLAINTEXT 74 1311860724 status: [GNUPG:] ERRSIG lll 17 2 01 1311860724 9 status: [GNUPG:] NO_PUBKEY lll status: [GNUPG:] DECRYPTION_OKAY status: [GNUPG:] GOODMDC status: [GNUPG:] END_DECRYPTION > Could there be an issue with the following? > > gpg: Can't check signature: public key not found When I decrypt it from the command line, this error message also shows up *after* the message is successfully decrypted.
> status: [GNUPG:] DECRYPTION_OKAY > status: [GNUPG:] GOODMDC > status: [GNUPG:] END_DECRYPTION Interesting, it tells the decryption is correct, if I understand the message correctly. Then it might fail a bit later. The problem is that messages which I encrypt to myself work properly, thus I do not know how to test/reproduce this on my machine :(
Today the original author sent me another encrypted email that evolution could not decrypt. This is what it prints to the console: $ CAMEL_DEBUG=gpg evolution status: [GNUPG:] ENC_TO aaa 16 0 status: [GNUPG:] USERID_HINT aaa Fabian Greffrath <fabian@greffrath.com> status: [GNUPG:] NEED_PASSPHRASE aaa bbb 16 0 status: [GNUPG:] GOOD_PASSPHRASE status: [GNUPG:] ENC_TO ccc 16 0 status: [GNUPG:] NO_SECKEY ccc status: [GNUPG:] BEGIN_DECRYPTION status: [GNUPG:] PLAINTEXT 74 1312234013 status: [GNUPG:] ERRSIG ddd 17 2 01 1312234013 9 status: [GNUPG:] NO_PUBKEY ddd status: [GNUPG:] DECRYPTION_OKAY status: [GNUPG:] GOODMDC status: [GNUPG:] END_DECRYPTION Instead of the mail it prints the following in red: Could not parse PGP/MIME message gpg: armor header: Version: GnuPG v1.4.11 (GNU/Linux) gpg: public key is aaa gpg: using subkey aaa instead of primary key bbb gpg: using subkey aaa instead of primary key bbb gpg: public key is ccc gpg: encrypted with ELG-E key, ID ccc gpg: encrypted with 2048-bit ELG-E key, ID aaa, created 2006-05-17 "Fabian Greffrath <fabian@greffrathagainnojunkpleasexyz.com>" gpg: AES256 encrypted data gpg: original file name='' gpg: Signature made Mon Aug 1 23:26:53 2011 CEST using DSA key ID ddd gpg: Can't check signature: public key not found The content of this mail is "less critical", i.e. it is empty and has been sent merely for testing purposes. Will it help to make the mail (or just the encrypted attachment) available?
This seems to be related to client which signed the message, or how it's done on that particular machine. Please ask the author to send me a test message encrypted by my GPG key (ID F3C36A0D), and that he/she writes a Bug number into message subject (as it can avoid blind removal to a junk/trash folder). I hope I'll be able to reproduce it with it here too.
Fabian, any updates on this, please? Maybe you can send me that message too, signed by your private key, because it's very similar to what you see, because I do not have your public key here.
Fabian, ping, can you please provide requested information ?
(In reply to comment #7) > Fabian, ping, can you please provide requested information ? I had a lengthy discussion with Milan via private mail in the mean time, but we were not yet able to reproduce the issue.
Hm. I guess I have to close this then. Please reopen if you have the information at hand.