From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Paris <eparis@redhat.com>,
Eduardo Otubo <otubo@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC] Continuous work on sandboxing
Date: Wed, 01 May 2013 11:30:00 -0400 [thread overview]
Message-ID: <518134F8.3020506@linux.vnet.ibm.com> (raw)
In-Reply-To: <11691265.oTT9LbASug@sifl>
On 05/01/2013 10:13 AM, Paul Moore wrote:
> On Tuesday, April 30, 2013 04:28:54 PM Corey Bryant wrote:
>> Just to be clear, I'm thinking you could launch guests in one of two
>> different seccomp sandboxed environments:
>>
>> 1) Using the existing and more permissive whitelist where every QEMU
>> feature works:
>>
>> qemu-kvm -sandbox on,default
>
> In general, I like the comma delimited list of sandbox filters/methods/etc.
> but I'm not sure we need to explicitly specify "default", it seems like "on"
> would be sufficient. It also preserved compatibility with what we have now.
>
Yes, I agree. This should definitely remain backward compatible.
--
Regards,
Corey Bryant
next prev parent reply other threads:[~2013-05-01 15:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 18:39 [Qemu-devel] [RFC] Continuous work on sandboxing Eduardo Otubo
2013-04-26 21:07 ` 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 [this message]
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=518134F8.3020506@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=eparis@redhat.com \
--cc=otubo@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.