From: "H. Peter Anvin" <hpa@zytor.com>
To: Kyle Moffett <kyle@moffetthome.net>
Cc: Greg KH <greg@kroah.com>,
Jari Ruusu <jariruusu@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: kernel.org tarball/patch signature files
Date: Tue, 25 Oct 2011 10:27:05 +0200 [thread overview]
Message-ID: <4EA672D9.106@zytor.com> (raw)
In-Reply-To: <CAGZ=bqKvb96VvZ5a+VJWZXKdr553n8SW2=JOLZS1fGY5KE7iZg@mail.gmail.com>
On 10/25/2011 06:31 AM, Kyle Moffett wrote:
>
> Unfortunately, while there are "pristine-gz" and "pristine-bz2" tools,
> there has not yet been developed a "pristine-xz" tool:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499489
>
> So it's not yet reasonably possible for the kernel.org archive, but
> sometime in the future it might become so.
>
There are a lot of strong reasons to NOT do so, however.
Any time we have something signed by a developer, we have something that
is precious and cannot be replicated by kernel.org staff.
Any time we have something signed by a robot, we have something that
people *will* misinterpret as having security properties that they don't
-- this has unfortunately been amply shown.
Compression formats evolve over time; right now we're concerned with gz,
bz2, and xz, but xz is brand new here and there may very well be new
things in the future.
It would be a very good thing for people to develop tools to run
compressors and decompressors in locked-down boxes. It should be
possible to run these kinds of programs without access to either network
or filesystem; only read from stdin and out on stdout (and presumably
stderr for errors.) This would solve problems for much more than just
kernel.org.
-hpa
next prev parent reply other threads:[~2011-10-25 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 11:17 kernel.org tarball/patch signature files Jari Ruusu
2011-10-23 11:37 ` Greg KH
2011-10-23 14:07 ` Jari Ruusu
2011-10-25 1:49 ` Greg KH
2011-10-25 4:31 ` Kyle Moffett
2011-10-25 8:27 ` H. Peter Anvin [this message]
2011-10-25 9:13 ` Valdis.Kletnieks
2011-10-25 9:32 ` H. Peter Anvin
2011-10-25 6:06 ` Jari Ruusu
2011-10-25 7:09 ` Greg KH
2011-10-25 8:09 ` Jari Ruusu
2011-10-25 7:28 ` Valdis.Kletnieks
2011-10-25 7:34 ` Greg KH
2011-10-24 17:18 ` Valdis.Kletnieks
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=4EA672D9.106@zytor.com \
--to=hpa@zytor.com \
--cc=greg@kroah.com \
--cc=jariruusu@users.sourceforge.net \
--cc=kyle@moffetthome.net \
--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;
as well as URLs for NNTP newsgroup(s).