From: Luca Barbieri <ldb@ldb.ods.org>
To: Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: How to send GnuPG signed mail to linux-kernel and maintainers?
Date: 26 May 2002 14:29:07 +0200 [thread overview]
Message-ID: <1022416147.4072.14.camel@ldb> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
Until now, I have sent mail to linux-kernel using an unmodified version
of Ximian Evolution with PGP sign turned on.
However, I've noticed that this causes the message to contain some
escape codes that, after reading a few RFCs and the source code, turn
out to be caused by the fact that Evolution, in compliance with RFC2015,
sends PGP-signed bodies as quoted-printable unless they are already
tagged as base64.
The rationale is that quoted-printable avoids any modification by
gateways that would obviously cause the signature to be invalid.
However, both the cs.helsinki.fi archive and Linus' scripts (he is
quoted in the L-K FAQ saying that he only wants unmangled text/plain) do
not properly support MIME transfer encodings.
Furthermore, if a gateway modifies a message, patches should also be
adversely affected, so this shouldn't be a problem.
Thus, among the possible solutions, the best one (and the one I'm
currently using, by patching Evolution) appears to be violating the RFC
and sending as 7-bit rather than as quoted-printable, risking
invalidation of the signatures by gateway modifications.
Not using digital signatures is obviously not an option since there is
no way to prove that a message was not authentic (if it contains a
trojan patch, for example).
Is this solution the best/recommended one?
Shouldn't this be added to the FAQ?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-05-26 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 12:29 Luca Barbieri [this message]
2002-05-26 12:50 ` How to send GnuPG signed mail to linux-kernel and maintainers? Dave Jones
2002-05-26 13:20 ` Luca Barbieri
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=1022416147.4072.14.camel@ldb \
--to=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.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