qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Otubo <otubo@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>,
	Eric Paris <eparis@redhat.com>, Paul Moore <pmoore@redhat.com>
Subject: [Qemu-devel] [RFC] Continuous work on sandboxing
Date: Fri, 26 Apr 2013 15:39:33 -0300	[thread overview]
Message-ID: <517AC9E5.3050204@linux.vnet.ibm.com> (raw)

Hello folks,

	Resuming the sandboxing work, I'd  like to ask for comments on the 
ideias I have:

1. Reduce whitelist to the optimal subset: Run various tests on Qemu 
with different configurations to reduce to the smallest syscall set 
possible; test and send a patch weekly (this is already being performed 
and a patch is on the way)

2. Introduce a second whitelist - the whitelist should be defined in 
libvirt and passed on to qemu or just pre defined in Qemu? Also remove 
execve() and avoid open() and socket() and its parameters - also 
wondering if (and how) we should pass the fd along from libvirt to qemu.

3. Debugging and/or learning mode - third party libraries still have the 
problem of interfering in the Qemu's signal mask. According to some 
previous discussions, perhaps patch all external libraries that mass up 
with this mask (spice, for example) is a way to solve it. But not sure 
if it worth the time spent. Would like to hear you guys.

Regards,

-- 
Eduardo Otubo
IBM Linux Technology Center

             reply	other threads:[~2013-04-26 18:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 18:39 Eduardo Otubo [this message]
2013-04-26 21:07 ` [Qemu-devel] [RFC] Continuous work on sandboxing Paul Moore
2013-04-26 22:17   ` Paolo Bonzini
2013-04-29 19:57     ` Eduardo Otubo
2013-04-29 21:06       ` Paolo Bonzini
2013-04-29 18:39   ` Eduardo Otubo
2013-04-29 19:24     ` Paul Moore
2013-04-29 22:02     ` Corey Bryant
2013-04-30 18:47       ` Eduardo Otubo
2013-04-30 20:28         ` Corey Bryant
2013-05-01 14:13           ` Paul Moore
2013-05-01 15:30             ` Corey Bryant
2013-04-29 21:52   ` Corey Bryant
2013-04-30 15:24     ` Paul Moore
2013-05-01 17:25       ` Eduardo Otubo
2013-05-01 18:04         ` Corey Bryant

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=517AC9E5.3050204@linux.vnet.ibm.com \
    --to=otubo@linux.vnet.ibm.com \
    --cc=berrange@redhat.com \
    --cc=eparis@redhat.com \
    --cc=pmoore@redhat.com \
    --cc=qemu-devel@nongnu.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).