Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: GnuPG: users

Slightly OT: PGP/MIME verification fails with new KMail2 and Thunderbird 13.0

 

 

GnuPG users RSS feed   Index | Next | Previous | View Threaded


mailinglisten at hauke-laging

Jul 9, 2012, 3:53 PM

Post #1 of 4 (225 views)
Permalink
Slightly OT: PGP/MIME verification fails with new KMail2 and Thunderbird 13.0

Hello,

I was just pointed at the problem that for the last months all of my
signatures are supposed to be bad. I use KMail which shows both the emails I
have sent and those I receive via this list as correctly signed. I just used
Thunderbird (13.0) to check and TB claims even (most but not all) of the
emails in my IMAP sent folder to have bad signatures. TB doesn't even
recognize the received emails as signed (just shows an "attachment").

The problem seems to be newline-related. I do not waste time by filing a bug
report for the wrong software... Thus maybe one of the MIME experts here can
tell me who's wrong. The KMail behaviour seems to have changed from KMail to
KMail2. KMail2 successfully verifies the TB emails.

Thunderbird puts one more empty line between the body and the MIME seperator:

#######################################
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814

--nextPart1869494.a4NpQxFzAE
Content-Type: application/pgp-signature; name="signature.asc"
#######################################

#######################################
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814


--------------enigDCF37498B4DFB4B1B81B232B
Content-Type: application/pgp-signature; name="signature.asc"
#######################################

I can manually successfully verify emails from both clients. So obviously one
of them feeds the wrong data into gpg (during signing or verification).


Hauke
--
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
Attachments: signature.asc (0.54 KB)


branko at majic

Jul 9, 2012, 11:43 PM

Post #2 of 4 (216 views)
Permalink
Re: Slightly OT: PGP/MIME verification fails with new KMail2 and Thunderbird 13.0 [In reply to]

As a curiosity, could you have both clients save the message in raw
format somewhere on the disks, and compare if they're the same with a
checksum?

Maybe there's some misbehavior with the line endings in terms of *nix
vs Winblow$ (so checking with cat -v would also be a good idea)? I know
that at some point I managed to corrupt an Apache configuration file
by copy/pasting stuff from KMail into terminal (but that was very long
time ago), there were some "invibisble" characters pasted in the
process.

On Tue, 10 Jul 2012 00:53:43 +0200
Hauke Laging <mailinglisten [at] hauke-laging> wrote:

> Hello,
>
> I was just pointed at the problem that for the last months all of my
> signatures are supposed to be bad. I use KMail which shows both the
> emails I have sent and those I receive via this list as correctly
> signed. I just used Thunderbird (13.0) to check and TB claims even
> (most but not all) of the emails in my IMAP sent folder to have bad
> signatures. TB doesn't even recognize the received emails as signed
> (just shows an "attachment").
>
> The problem seems to be newline-related. I do not waste time by
> filing a bug report for the wrong software... Thus maybe one of the
> MIME experts here can tell me who's wrong. The KMail behaviour seems
> to have changed from KMail to KMail2. KMail2 successfully verifies
> the TB emails.
>
> Thunderbird puts one more empty line between the body and the MIME
> seperator:
>
> #######################################
> PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
>
> --nextPart1869494.a4NpQxFzAE
> Content-Type: application/pgp-signature; name="signature.asc"
> #######################################
>
> #######################################
> PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
>
>
> --------------enigDCF37498B4DFB4B1B81B232B
> Content-Type: application/pgp-signature; name="signature.asc"
> #######################################
>
> I can manually successfully verify emails from both clients. So
> obviously one of them feeds the wrong data into gpg (during signing
> or verification).
>
>
> Hauke



--
Branko Majic
Jabber: branko [at] majic
Please use only Free formats when sending attachments to me.

Бранко Мајић
Џабер: branko [at] majic
Молим вас да додатке шаљете искључиво у слободним форматима.

_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users


dougb at dougbarton

Jul 10, 2012, 1:58 AM

Post #3 of 4 (216 views)
Permalink
Re: Slightly OT: PGP/MIME verification fails with new KMail2 and Thunderbird 13.0 [In reply to]

On Tue, 10 Jul 2012, Hauke Laging wrote:

> Hello,
>
> I was just pointed at the problem that for the last months all of my
> signatures are supposed to be bad. I use KMail which shows both the emails I
> have sent and those I receive via this list as correctly signed. I just used
> Thunderbird (13.0) to check and TB claims even (most but not all) of the
> emails in my IMAP sent folder to have bad signatures. TB doesn't even
> recognize the received emails as signed (just shows an "attachment").
>
> The problem seems to be newline-related. I do not waste time by filing a bug
> report for the wrong software... Thus maybe one of the MIME experts here can
> tell me who's wrong. The KMail behaviour seems to have changed from KMail to
> KMail2. KMail2 successfully verifies the TB emails.

There is a difference in how KMail deals with EOL whitespace, I have an
exception for it in my PGP filters for Alpine. I don't know what's
different between KMail 1 and 2, but I'm glad you raised this. I can use
my filters to verify your KMail 1.x messages, but Enigmail refuses to
recognize that they contain valid signed messages. However I cannot
verify your latest message using KMail 2, so clearly there is something
different.

> Thunderbird puts one more empty line between the body and the MIME seperator:

I'm not sure it's Thunderbird, I think it's Mailman (at least that was
the consensus from previous discussion). Have you compared the raw
message in your Sent mail folder to the one from the list? Also, if you
look at your message in the archives, it seems to be similarly
malformed.

> I can manually successfully verify emails from both clients. So obviously one
> of them feeds the wrong data into gpg (during signing or verification).

Don't rule out "all of the above." :)

Seriously though, can you do me a favor and send me copies of the _raw_
messages from your Sent mail folder, and the message you received from
the list (the one I'm responding to is fine)? Please compress them
somehow (tgz is fine) so that they don't get molested in transit.
That'll help me sort out how whitespace is being handled differently in
KMail 2.

Doug

--

It's always a long day; 86400 doesn't fit into a short.

Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/


_______________________________________________
Gnupg-users mailing list
Gnupg-users [at] gnupg
http://lists.gnupg.org/mailman/listinfo/gnupg-users


mailinglisten at hauke-laging

Jul 10, 2012, 5:23 AM

Post #4 of 4 (215 views)
Permalink
Re: Slightly OT: PGP/MIME verification fails with new KMail2 and Thunderbird 13.0 [In reply to]

Am Di 10.07.2012, 08:43:55 schrieb Branko Majic:
> As a curiosity, could you have both clients save the message in raw
> format somewhere on the disks, and compare if they're the same with a
> checksum?

A checksum is not neccessary, it's obviously not the same. KMail stores the
files with \n line endings instead of \r\n. In order to successfully verify
the signature I had to convert the KMail file to \r\n and to remove the \r\n
(both) on the last line until I added a \n to my text signature.

...

I just checked the files after the conversion to \r\n. There were more
differences (probably not relevant for this problem). The KMail file has an
addidional line at the beginning:

>From hauke [at] laging Mon, 09 Jul 2012 20:06:34 +0200

Furthermore the KMail file has \r\n at the end of the last line, the TB file
does not. But the signed part and the signature are stored identically.


Hauke
--
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
Attachments: signature.asc (0.54 KB)

GnuPG users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.