From: Paul Moore <pmoore@redhat.com>
To: Namsun Ch'o <namnamc@safe-mail.net>
Cc: qemu-devel@nongnu.org, eduardo.otubo@profitbricks.com
Subject: Re: [Qemu-devel] [PATCH v2] Add argument filters to the seccomp sandbox
Date: Mon, 28 Sep 2015 14:24:52 -0400 [thread overview]
Message-ID: <206215295.9GP3EI1jzg@sifl> (raw)
In-Reply-To: <N1-oHzcQw7dPv@Safe-mail.net>
On Saturday, September 26, 2015 01:06:57 AM Namsun Ch'o wrote:
> > I've suggested this in the past but to my knowledge no has done any work
> > in this direction, including myself. Despite the lack of progress, I still
> > think this is a very worthwhile idea.
>
> Which is exactly why I think a configuration file would be the best option
> instead of --enable-syscalls=foo,bar,baz. It would allow someone to easily
> customize their policy without needing to create a patch, or wait on QEMU
> developers to do work on it.
To be clear, I'm not suggesting "--enable-syscalls=foo,bar,...", what I'm
suggesting is a decomposition of the current filter list into blocks of
syscalls that are needed to enable specific functionality. For example, if
you enable audio support at runtime a set of syscalls will be added to the
filter whitelist, if you enable a network device a different set of syscalls
will be added to the filter, and so on.
I think having an admin specified filter, either via a command line or
configuration file, is a step in the wrong direction.
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-09-28 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-26 5:06 [Qemu-devel] [PATCH v2] Add argument filters to the seccomp sandbox Namsun Ch'o
2015-09-28 18:24 ` Paul Moore [this message]
[not found] <d55ad1eed872006f0634c3e0067553a5@airmail.cc>
2015-10-01 7:17 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2015-09-30 6:41 Namsun Ch'o
2015-10-01 5:58 ` Markus Armbruster
2015-09-29 3:14 Namsun Ch'o
2015-09-29 15:38 ` Eduardo Otubo
2015-09-29 22:12 ` Paul Moore
2015-09-28 21:34 Namsun Ch'o
2015-09-29 1:19 ` Paul Moore
2015-09-25 4:53 Namsun Ch'o
2015-09-25 17:03 ` Paul Moore
2015-09-11 0:54 namnamc
2015-09-24 9:59 ` 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=206215295.9GP3EI1jzg@sifl \
--to=pmoore@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).