After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 219789 - GPG Key not being read properly?
GPG Key not being read properly?
Status: RESOLVED DUPLICATE of bug 217540
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-01-31 22:26 UTC by Steven Hatfield
Modified: 2002-10-06 23:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Steven Hatfield 2002-01-31 22:26:35 UTC
Package: Evolution
Priority: Normal
Version: 1.0.1
Synopsis: GPG Key not being read properly?
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
I have a friend's GnuPG key in my keyring, and when I click on the lock,
it says that his signature is invalid:

	This message is digitally signed but can not be proven to be
authentic.

gpg: armor header: Version: GnuPG v1.0.6 (GNU/Linux)
gpg: armor header: Comment: For info see http://www.gnupg.org
gpg: Signature made Thu 31 Jan 2002 04:13:16 PM EST using DSA key ID
A9D36482
gpg: BAD signature from "Fred A. Miller <fm@cupserv.org>"

-EOF-

If I open this message in KMail, the signature verifies fine...

Evolution still rocks, good work guys!


Comment 1 Steven Hatfield 2002-02-04 00:49:53 UTC
I have done some more research, and have found that Evolution 
doesn't handle the GPG portion of messages right. KMail doesn't 
understand the gobbledygook, so refuses to acknowledge that the 
message is signed. Therefore, GPG encrypted or signed messages do 
not work between KMail and Evolution. (and probably not between 
Evolution and any other GPG/PGP capable email client).

Here is an example of the GPG signature area of an email GPG signed 
with KMail:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Test message - signed by me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Xc5C3pOz+fmMqdsRAoHrAJ9g7IhcUwSt1kTymHjYuGvqMuZ5FgCeJPmS
N48c7jTVKCURM/ZjYComKJE=
=61Qt
-----END PGP SIGNATURE-----

Now here is Evolution:

--=-d7SFfukpdqc8RycABLBg
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

Test message, signed by me

--=-d7SFfukpdqc8RycABLBg
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA8Xc3y3pOz+fmMqdsRAiANAJ0SDB/S5yYmzCC5NVSrmxMsArv59gCfSx32
/g473bKEzoGuJEMcOXE1wg8=
=hib1
-----END PGP SIGNATURE-----

--=-d7SFfukpdqc8RycABLBg--

See the extra gunk in there? That's confusing other GPG capable 
email readers and not allowing me to communicate with them :(

Thanks, and have a great day!
Comment 2 Gerardo Marin 2002-04-07 21:15:11 UTC

*** This bug has been marked as a duplicate of 217540 ***
Comment 3 Jeffrey Stedfast 2002-10-06 23:18:47 UTC
KMail uses inline pgp (which is not meant for use with mail) while
Evolution uses the PGP/MIME standard form.

see http://www.ietf.org/rfcs/rfc3156.txt for details

(that url might not be right, but if you go to www.ietf.org and search
for 3156 it will give you the correct url)