From: Rusty Russell <rusty@rustcorp.com.au>
To: Sasha Levin <levinsasha928@gmail.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
Pekka
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: Secure KVM
Date: Mon, 07 Nov 2011 10:37:44 +1030 [thread overview]
Message-ID: <877h3cu75a.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1320612020.3299.22.camel@lappy>
On Sun, 06 Nov 2011 22:40:20 +0200, Sasha Levin <levinsasha928@gmail.com> wrote:
> The solution is also simple to explain: Split the devices into different
> processes and use seccomp to sandbox each device into the exact set of
> resources it needs to operate, nothing more and nothing less.
lguest does a process per device. Actually, it uses clone for legacy
reasons, but I have a patch which changes it to processes.
It works well, and it's *simple*. I suggest looking at
Documentation/virtual/lguest/lguest.c.
Good luck!
Rusty.
next prev parent reply other threads:[~2011-11-07 1:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 20:40 Secure KVM Sasha Levin
2011-11-07 0:07 ` Rusty Russell [this message]
2011-11-07 6:29 ` Sasha Levin
2011-11-07 6:37 ` Pekka Enberg
2011-11-07 6:46 ` Sasha Levin
2011-11-07 7:03 ` Pekka Enberg
2011-11-07 22:49 ` Rusty Russell
2011-11-07 9:26 ` Avi Kivity
2011-11-07 10:17 ` Sasha Levin
2011-11-07 10:27 ` Avi Kivity
2011-11-07 11:27 ` Stefan Hajnoczi
2011-11-07 12:40 ` Sasha Levin
2011-11-07 12:51 ` Avi Kivity
2011-11-07 14:56 ` Stefan Hajnoczi
2011-11-07 17:43 ` Anthony Liguori
2011-11-07 18:41 ` Avi Kivity
2011-11-07 17:39 ` Anthony Liguori
2011-11-07 18:43 ` Avi Kivity
2011-11-07 19:07 ` Anthony Liguori
2011-11-07 19:54 ` Avi Kivity
2011-11-07 22:56 ` Rusty Russell
2011-11-07 17:37 ` Anthony Liguori
2011-11-07 17:52 ` Sasha Levin
2011-11-07 18:03 ` [Qemu-devel] " Anthony Liguori
2011-11-07 23:06 ` Rusty Russell
2011-11-08 19:51 ` Will Drewry
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=877h3cu75a.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=aarcange@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.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