From: fche@redhat.com (Frank Ch. Eigler)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Greg KH <greg@kroah.com>, Piotr Hosowicz <piotr@hosowicz.com>,
linux-kernel@vger.kernel.org, John Hawley <warthog19@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Linux 3.0.7 now on kernel.org
Date: Sun, 23 Oct 2011 10:18:17 -0400 [thread overview]
Message-ID: <y0mmxcrx046.fsf@fche.csb> (raw)
In-Reply-To: <4EA4151A.4030605@zytor.com> (H. Peter Anvin's message of "Sun, 23 Oct 2011 15:22:34 +0200")
"H. Peter Anvin" <hpa@zytor.com> writes:
> [...]
> Signing the compressed file makes the compression "precious". It also
> means that the developer has to sign each.
>
> It's not significantly "more handy" either... you can do something like:
> xz -cd file.xz | gpg --verify file.sign -
On the other hand, it forces someone to decompress an untrustworthy
file in order to check its signature. Should there ever be a security
exploit in any of these decompressors, this practice would aid
triggering it.
- FChE
prev parent reply other threads:[~2011-10-23 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-23 8:31 Linux 3.0.7 now on kernel.org Greg KH
2011-10-23 12:24 ` Piotr Hosowicz
2011-10-23 12:29 ` Greg KH
2011-10-23 13:22 ` H. Peter Anvin
2011-10-23 14:18 ` Frank Ch. Eigler [this message]
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=y0mmxcrx046.fsf@fche.csb \
--to=fche@redhat.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr@hosowicz.com \
--cc=torvalds@linux-foundation.org \
--cc=warthog19@gmail.com \
/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).