[Bug 305171] New: nearly all openpgp signatures are invalid

Hauke Laging hauke at laging.de
Wed Aug 15 01:06:39 BST 2012


https://bugs.kde.org/show_bug.cgi?id=305171

            Bug ID: 305171
          Severity: major
           Version: unspecified
          Priority: NOR
          Assignee: kdepim-bugs at kde.org
           Summary: nearly all openpgp signatures are invalid
    Classification: Unclassified
                OS: Linux
          Reporter: hauke at laging.de
          Hardware: openSUSE RPMs
            Status: UNCONFIRMED
         Component: crypto
           Product: kmail2

Since KMail2 nearly all (more than 90%) of my email signatures are shown as
invalid by other mail clients. I tried to understand which software is buggy by
reading the rfc but I am still not sure. Most probably it is KMail2. KMail2
shows these signatures as correct.

The problem seems to be a missing newline. The MIME seperator is placed
directly after my last signature line:

########################
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
--nextPart20694277.1dnrQtI15C
########################

In earlier versions of KMail (and in Thunderbird) there was en empty line in
between:
########################
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814

--nextPart3343035.S6mqRQsH14
########################

The signature is not completely wrong. If I save the mail as a file, convert it
to DOS newline and add a newline to the end of the data block then I can verify
the signature by gpg. So it is obvously just a formatting problem.

It seems not to make a difference whether the signature text ends with a
newline.

Reproducible: Always

Steps to Reproduce:
1. Just send a signed email in PGP/MIME format.

Actual Results:  
Signature is not recognized by other mail clients.

Expected Results:  
A compatible signature (or rather: compatible MIME formatting of it).

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list