[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EBB94D9.30906@redhat.com>
Date: Thu, 10 Nov 2011 11:09:45 +0200
From: Avi Kivity <avi@...hat.com>
To: Sasha Levin <levinsasha928@...il.com>
CC: Markus Armbruster <armbru@...hat.com>,
Pekka Enberg <penberg@...nel.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Pekka Enberg <penberg@...helsinki.fi>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
On 11/10/2011 11:04 AM, Sasha Levin wrote:
> On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <armbru@...hat.com> wrote:
> > Sasha Levin <levinsasha928@...il.com> writes:
> >
> >> On Thu, Nov 10, 2011 at 9:57 AM, Markus Armbruster <armbru@...hat.com> wrote:
> > [...]
> >>> Start with a clean read/write raw image. Probing declares it raw.
> >>> Guest writes QCOW signature to it, with a backing file of its choice.
> >>>
> >>> Restart with the same image. Probing declares it QCOW2. Guest can read
> >>> the backing file. Oops.
> >>
> >> Thats an excellent scenario why you'd want to have 'Secure KVM' with
> >> seccomp filters :)
> >
> > Yup.
> >
> > For what it's worth, sVirt (use SELinux to secure virtualization)
> > mitigates the problem. Doesn't mean we couldn't use "Secure KVM".
>
> How does it do it do that? You have a hypervisor trying to read
> arbitrary files on the host FS, no?
Trying and failing. sVirt will deny access to all files except those
explicitly allowed by libvirt.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists