GNOME Bugzilla – Bug 386468
gpg encrypted message not shown
Last modified: 2009-10-16 08:37:03 UTC
Please describe the problem: I'm going to attach a message that is encrypted to the following test key: http://johannes.sipsolutions.net/files/testkey.asc Said message is not shown at all when viewed in evolution even though it contains some text! Additionally, the message is signed by my key as gpg shows: johannes:~$ gpg --decrypt /tmp/msg You need a passphrase to unlock the secret key for user: "Some Tester (never use this key) <testkey@example.org>" 1024-bit ELG-E key, ID B6F004FF, created 2006-12-16 (main key ID 4C6B3A42) gpg: encrypted with 1024-bit ELG-E key, ID B6F004FF, created 2006-12-16 "Some Tester (never use this key) <testkey@example.org>" This is just a short test message. gpg: Signature made Sat 16 Dec 2006 12:27:37 PM CET using DSA key ID 9AB78CA5 gpg: Good signature from "Johannes Berg <johannes@sipsolutions.net>" gpg: [...] But evolution claims that it is not signed! Steps to reproduce: 1. import the secret and public key from http://johannes.sipsolutions.net/files/testkey.asc 2. import my public key 9AB78CA5 from a keyserver 3. import the message I'm going to attach 4. view the message Actual results: "encrypted" and lock with green check is displayed but no message contents, clicking the lock shows "not signed" Expected results: the message contents is displayed, the lock as well, and clicking the lock shows that it is encrypted to my key Does this happen every time? yes Other information:
Created attachment 78467 [details] test message (as mbox) this is the test message you can import
Created attachment 78468 [details] private/public key pair the message is encrypted to this is the key pair just so that it's stored along with the bug. It'd be nice if there was a key pair publically available for the purpose of reporting bugs with encrypted mail, feel free to use this one
made a separate issue out of the "claims it is not signed" in bug 386474
Created attachment 127938 [details] [review] proposed eds patch for evolution-data-server; The reason is that the usual encrypted text begins with headers like Content-Type and Content-Transfer-Encoding, but that yours isn't. Actually, I'm not sure how much it is a bug or not.
I would have thought Content-Type: multipart/encrypted; boundary="=-=-="; protocol="application/pgp-encrypted" would be enough?
Nono, those lines are supposed to be inside the encrypted part. When evolution itself encrypts text, it's like this (I do not have exact values handy, but very similarly like this): Content-Type: text/plain Content-Transfer-Encoding: 7bit This is a short message text. The important part is definition of the content type of the encrypted part, so Evolution (and other clients, I guess) will know what to do with it. You know, it can be basically anything, even some image or an external document. Ehm, which reminds me to set the content type in the patch to the application/octet-stream and mark it as inline, thus it will be shown as an attachment, but the opened one. (It doesn't worth to resend a patch, does it?)
Johannes, can you test the patch, Milan provided ?
Created commit eaaf8dd in eds master (2.29.1+)