From: Dave Jones <davej@suse.de>
To: Luca Barbieri <ldb@ldb.ods.org>
Cc: Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: How to send GnuPG signed mail to linux-kernel and maintainers?
Date: Sun, 26 May 2002 14:50:18 +0200 [thread overview]
Message-ID: <20020526145018.H16102@suse.de> (raw)
In-Reply-To: <1022416147.4072.14.camel@ldb>
On Sun, May 26, 2002 at 02:29:07PM +0200, Luca Barbieri wrote:
> 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).
Just because a patch has been signed does not mean it somehow manages
to bypass peer review.
If the patch is correct, it gets applied. If it's not obviously correct,
it gets reviewed by someone more familiar with the code.
Some people have a hard enough time getting patches they believe are
legitimate features/fixes past Al Viro, Dave Miller and the likes.
The chances of a trojan patch getting past them is I would hope, extremely minimal.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-05-26 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-26 12:29 How to send GnuPG signed mail to linux-kernel and maintainers? Luca Barbieri
2002-05-26 12:50 ` Dave Jones [this message]
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=20020526145018.H16102@suse.de \
--to=davej@suse.de \
--cc=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