From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Broken display of clearsigned PGP message
Date: Fri, 13 Oct 2006 17:31:15 +0200 [thread overview]
Message-ID: <v9odsgtepo.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87zmc0thhh.fsf@gate450.dyndns.org>
On Fri, Oct 13 2006, Andreas Seltenreich wrote:
>> I'm not sure if this message is legal according to RFC 2440. In 6.2
>> it states that Armor Headers are followed by a blank line, which is
>> defined as "zero-length, or containing only whitespace", however in
>> 7. it uses the term "empty line" when describing Armor Headers in
>> cleartext signatures.
>>
>> IMHO we should follow "be liberal in what you accept" here, especially
>> since GnuPG considers the message legal. Should I apply the attached
>> patch to v5-10 and HEAD? Can anyone imagine regressions?
>
> I just realized that with the current behavior, an attacker could
> completely replace the text within Gnus' signed-message markup with
> his own message without interfering with the verification process. So
> I guess it is hard to make the situation worse... Will commit the
> patch.
Thanks.
I'd suggest to add a rather detailed explanation about this problem
and the relevant RFC in `mm-uu-pgp-signed-extract-1'.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-10-13 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 5:31 Andreas Seltenreich
2006-10-13 14:31 ` Andreas Seltenreich
2006-10-13 15:31 ` Reiner Steib [this message]
2006-11-18 3:40 ` Andreas Seltenreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9odsgtepo.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).