From: Bastian Blank <bastian@waldi.eu.org>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH] pv-grub: Support bzip2, xz and lzo compressed kernels
Date: Tue, 26 Feb 2013 23:25:02 +0100 [thread overview]
Message-ID: <20130226222502.GB27098@waldi.eu.org> (raw)
In-Reply-To: <1357303220.14291.11.camel@zakaz.uk.xensource.com>
On Fri, Jan 04, 2013 at 12:40:20PM +0000, Ian Campbell wrote:
> On Fri, 2013-01-04 at 12:33 +0000, Bastian Blank wrote:
> > Is there a reason not to use the implementations used by the hypervisor?
> Decompressing a potentially untrusted compressed file in the context of
> the hypervisor would open you up to all sorts of security issues. One of
> the points of pv-grub is that the untrusted code runs only with guest
> privileges.
This was not what I meant, but you realized that already.
Anyway, I have some not really nice patches that integrate the
hypervisor bzip2, lzma, xz and lzo code into pv-grub. gzip is not
handled via this code path.
Bastian
--
Insufficient facts always invite danger.
-- Spock, "Space Seed", stardate 3141.9
next prev parent reply other threads:[~2013-02-26 22:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 11:56 [PATCH] pv-grub: Support bzip2, xz and lzo compressed kernels Ian Campbell
2013-01-04 12:15 ` Samuel Thibault
2013-01-04 12:43 ` Ian Campbell
2013-01-04 23:42 ` Samuel Thibault
2013-09-10 18:51 ` Matt Wilson
2013-09-10 19:05 ` Bastian Blank
2013-09-10 19:14 ` Matt Wilson
2013-01-04 12:33 ` Bastian Blank
2013-01-04 12:40 ` Ian Campbell
2013-02-26 22:25 ` Bastian Blank [this message]
2013-02-26 22:30 ` [RFC] libxc: Move compression support into own file Bastian Blank
2013-02-26 22:32 ` [RFC] libxc: Add trusted decompressors Bastian Blank
2013-02-27 12:17 ` Ian Campbell
2013-02-27 12:44 ` Bastian Blank
2013-02-27 14:28 ` Ian Campbell
2013-03-04 10:33 ` George Dunlap
2013-03-04 11:02 ` Tim Deegan
2013-03-12 15:21 ` Ian Campbell
2013-03-02 20:16 ` [PATCH] " Bastian Blank
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=20130226222502.GB27098@waldi.eu.org \
--to=bastian@waldi.eu.org \
--cc=xen-devel@lists.xen.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).