Bug 52328 - GPG KMail unable to verify old signature
Summary: GPG KMail unable to verify old signature
Status: RESOLVED DUPLICATE of bug 51180
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-26 20:49 UTC by Konrad Rosenbaum
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
One example of a mail shown erroneously. (3.50 KB, application/octet-stream)
2002-12-27 12:32 UTC, Konrad Rosenbaum
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Konrad Rosenbaum 2002-12-26 20:49:10 UTC
Version:           1.5 (using KDE KDE 3.0.99)
Installed from:    Compiled From Sources
Compiler:          gcc 3.2 
OS:          Linux

I just switched from KDE 3.0.3 to KDE 3.1RC5 (KMail 1.5). My GPG Signatures that were shown to be perfectly OK few hours ago are now shown as invalid. When saving the Message and filtering it through gpg by hand GPG shows:

gpg: CRC error; 206c9c - dc3206
gpg: quoted printable character in armor - probably a buggy MTA has been used

When filtering it through mimedecode first GPG verifies the signature as valid.

The messages affected contain quoted printable characters. It seems to me KMail has changed the order of filters.

The active GPG-Filters are:
internal OpenGPG
OpenGPG
S/MIME

Although the new behaviour seems more correct to me KMail should be able to verify older Mails.

One of those mails can be found here:
original: http://www.rosenbaum.dyndns.org/test4.asc
after mimedecode: http://www.rosenbaum.dyndns.org/test5.asc
Comment 1 Ingo Klöcker 2002-12-27 01:56:12 UTC
It's very likely that this bug is the same as bug #51180. 

*** This bug has been marked as a duplicate of 51180 ***
Comment 2 Konrad Rosenbaum 2002-12-27 12:20:53 UTC
Subject: Re:  GPG KMail unable to verify old signature

> *** This bug has been marked as a duplicate of 51180 ***

It's no duplicate: the mail does not have attachments and all the underscores 
are perfectly ok in this mail, the QP-encoded characters where =20 (space), 
=E4 (
Comment 3 Konrad Rosenbaum 2002-12-27 12:31:17 UTC
Sorry, I was wrong, it does contain a Content-Transfer-Encoding:-Header. 
Comment 4 Konrad Rosenbaum 2002-12-27 12:32:59 UTC
Created attachment 657 [details]
One example of a mail shown erroneously.
Comment 5 Konrad Rosenbaum 2002-12-27 12:33:36 UTC
see above. 
Comment 6 Ingo Klöcker 2002-12-27 18:12:15 UTC
Subject: Re:  GPG KMail unable to verify old signature

The message you sent us contains underscores and I could verify the 
signature (it's good).
Do you really see underscores left and right of the word "immer" when 
you select the message you sent us?

Comment 7 Konrad Rosenbaum 2002-12-27 23:54:43 UTC
Subject: Re:  GPG KMail unable to verify old signature

> Do you really see underscores left and right of the word "immer" when
> you select the message you sent us?

OOps, that's it: no I don't see the underscores, I see extra spaces. Sorry for 
the confusion. I rechecked some other mails: all the ones with "invalid 
signatures" contain some underscores which cannot be seen in KMail. However, 
underscores _are_ (there they were again) shown if the mail was encrypted 
also and the signature is also valid then.

	Konrad

Comment 8 Konrad Rosenbaum 2002-12-28 00:05:41 UTC
Subject: Re:  GPG KMail unable to verify old signature

Couriously enough underscores do work if sent from a the same KMail as it is 
read with, although they are sent as underscores, not as =5F.

Comment 9 Ingo Klöcker 2002-12-28 11:34:17 UTC
So it is a duplicate of 51180. BTW, the problem is actually caused by a compiler bug. 

*** This bug has been marked as a duplicate of 51180 ***