From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Namsun Ch'o <namnamc@Safe-mail.net>,
qemu-devel@nongnu.org, eduardo.otubo@profitbricks.com
Subject: Re: [Qemu-devel] [PATCH] Add syscalls for -runas and -chroot to the seccomp sandbox
Date: Fri, 2 Oct 2015 09:30:47 +0100 [thread overview]
Message-ID: <20151002083047.GA28469@redhat.com> (raw)
In-Reply-To: <87r3leztbr.fsf@blackfin.pond.sub.org>
On Thu, Oct 01, 2015 at 02:06:32PM +0200, Markus Armbruster wrote:
> "Namsun Ch'o" <namnamc@Safe-mail.net> writes:
>
> > The seccomp sandbox doesn't whitelist setuid, setgid, or setgroups, which are
> > needed for -runas to work. It also doesn't whitelist chroot, which is needed
> > for the -chroot option. Unfortunately, QEMU enables seccomp before it drops
> > privileges or chroots, so without these whitelisted, -runas and -chroot cause
> > QEMU to be killed with -sandbox on. This patch adds those syscalls.
>
> Should it enable seccomp a bit later?
Yeah, I think it would be better to move the seccomp enablement later.
Adding setuid and chroot to the allow list is pretty strongly undesirable
from a security protection POV.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2015-10-02 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 4:36 [Qemu-devel] [PATCH] Add syscalls for -runas and -chroot to the seccomp sandbox Namsun Ch'o
2015-10-01 12:06 ` Markus Armbruster
2015-10-02 8:30 ` Daniel P. Berrange [this message]
2015-10-02 10:05 ` Markus Armbruster
2015-10-02 14:08 ` Eduardo Otubo
2015-10-02 14:15 ` Daniel P. Berrange
2015-10-02 15:36 ` Eduardo Otubo
2015-10-08 13:34 ` Eduardo Otubo
-- strict thread matches above, loose matches on Subject: below --
2015-10-02 0:17 namnamc
2015-10-09 2:09 namnamc
2015-10-09 6:54 ` Markus Armbruster
2015-10-09 7:24 ` Eduardo Otubo
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=20151002083047.GA28469@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eduardo.otubo@profitbricks.com \
--cc=namnamc@Safe-mail.net \
--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).