From: Werner Koch <wk@gnupg.org>
Subject: trailing spaces in signed mails
Date: Fri, 17 Dec 2004 13:03:17 +0100 [thread overview]
Message-ID: <87y8fx9loa.fsf@wheatstone.g10code.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Hi!
After the release of gnupg 1.4.0 a lot of people complained that they
were not able to verify my signature anymore. The reason for this is
due to a change in OpenPGP and thus gpg to not strip trailing white
spaces anymore for signing. PGP/MIME (rfc 3156) defines rules on how
to protect against this problem (most PGG and OpenPGP implementations
did it differently in the past) but these rules are not follwed by
mml2015. In particular, rfc 3156 states:
Additionally, implementations MUST make sure that no trailing
whitespace is present after the MIME encoding has been applied.
the example given also states:
& Also, in some cases it might be desirable to encode any =20
& trailing whitespace that occurs on lines in order to ensure =20
& that the message signature is not invalidated when passing =20
& a gateway that modifies such whitespace (like BITNET). =20
This message is signed and the "-- " before the signature lines should
have been send as "--=20". I suggest to convert the last of a run of
trailing spaces to QP. My Gnus version is v5.10.6.
Shalom-Salam,
Werner
--
Werner Koch <wk@gnupg.org>
The GnuPG Experts http://g10code.com
Free Software Foundation Europe http://fsfeurope.org
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next reply other threads:[~2004-12-17 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 12:03 Werner Koch [this message]
2004-12-27 1:23 ` Simon Josefsson
2004-12-27 2:06 ` Simon Josefsson
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=87y8fx9loa.fsf@wheatstone.g10code.de \
--to=wk@gnupg.org \
/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).