[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-users
Subject:    Re: Keyservers
From:       Ingo =?utf-8?q?Kl=C3=B6cker?= <kloecker () kde ! org>
Date:       2011-03-20 17:28:06
Message-ID: 201103201828.07200 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Sunday 20 March 2011, Charly Avital wrote:
> Ingo Klöcker wrote the following on 3/20/11 11:43 AM:
> > I doubt this very much because the encoding surely happens before
> > the signing.
> > 
> > 
> > Regards,
> > Ingo
> 
> In my post, I also indicated that there was a string --=20 between
> the actual text and the signature disclaimer ""CONFIDENTIALITY
> NOTICE: This e-mail...."

Well, that's the "standard" signature separator: 2 dashes followed by a 
space. To preserve this trailing space Thunderbird/enigmail does the 
right thing and encodes it.


> After Jonathan disabled that signature add-on, his signed messages
> verified.

Yeah, well. Even though Jonathan disabled the signature his message is 
still quoted-printable encoded. As are my messages. So, quoted-printable 
encoding does not seem to be the problem.

Also, Jonathan's message "Re: what are the sub keys" does not have a 
signature. Still the signature is broken. What the two messages with 
broken signatures seem to have in common is the attached key. Maybe 
that's what is causing the problems.


Regards,
Ingo

-- 
Test signature. Please ignore.

["signature.asc" (application/pgp-signature)]

_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


[prev in list] [next in list] [prev in thread] [next in thread]