From: Ivan Boldyrev <boldyrev+nospam@cgitftp.uiggm.nsc.ru>
Subject: Re: Trailing whitespace and PGP/MIME
Date: Tue, 30 Dec 2003 15:04:44 +0600 [thread overview]
Message-ID: <gmr7c1x328.ln2@ibhome.cgitftp.uiggm.nsc.ru> (raw)
In-Reply-To: <m3fzf3hwz4.fsf@defun.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
On 8608 day of my life Jesper Harder wrote:
> Currently Gnus violates this requirement in RFC 3156 (MIME Security
> with OpenPGP):
>
> implementations MUST make sure that no trailing whitespace is
> present after the MIME encoding has been applied.
Note: RFC 3156 describes PGP/MIME only.
> Fixing it the obvious way would, however, break the intention of this
> change:
>
> 2003-10-27 Simon Josefsson <jas@extundo.com>
>
> * mm-bodies.el (mm-body-encoding): Don't use QP when message body
> only consists of short lines and ASCII, when
> mm-use-ultra-safe-encoding. Refer to 'About foo' thread in
> gnus-bug, e.g. <ilullrg4k7p.fsf@extundo.com>, for more discussion.
> This make it possible to pipe the raw RFC 822 message into 'gpg'
> and have the signature work.
It's true only for Plain PGP. PGP/MIME uses detached signatures, that
cannot be verified with piping.
My opinion is that whitespaces must be removed from PGP/MIME-encoded
messages but not from Plain PGP-encoded ones. But it is current
state of Gnus, isn't it?
BTW, is gnus-bug archived somewhere?
--
Ivan Boldyrev
Today is the first day of the rest of your life.
[-- Attachment #2: Type: application/pgp-signature, Size: 480 bytes --]
next prev parent reply other threads:[~2003-12-30 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 2:15 Jesper Harder
2003-12-30 9:04 ` Ivan Boldyrev [this message]
2003-12-30 11:31 ` Simon Josefsson
2003-12-30 13:12 ` Ivan Boldyrev
2003-12-30 11:05 ` Simon Josefsson
2003-12-30 13:02 ` Jesper Harder
2003-12-30 20:56 ` Simon Josefsson
2003-12-30 23:29 ` Jesper Harder
2003-12-30 23:52 ` Simon Josefsson
2003-12-31 0:01 ` Russ Allbery
2003-12-30 23:46 ` Russ Allbery
2003-12-31 0:05 ` Simon Josefsson
2003-12-31 2:26 ` Russ Allbery
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=gmr7c1x328.ln2@ibhome.cgitftp.uiggm.nsc.ru \
--to=boldyrev+nospam@cgitftp.uiggm.nsc.ru \
/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).