[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110624202015.GD32221@outflux.net>
Date: Fri, 24 Jun 2011 13:20:15 -0700
From: Kees Cook <kees.cook@...onical.com>
To: Will Drewry <wad@...omium.org>
Cc: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
djm@...drot.org, segoon@...nwall.com, mingo@...e.hu,
rostedt@...dmis.org, jmorris@...ei.org, fweisbec@...il.com,
tglx@...utronix.de, scarybeasts@...il.com,
Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paul.mckenney@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Howells <dhowells@...hat.com>,
Eric Paris <eparis@...hat.com>,
Borislav Petkov <borislav.petkov@....com>,
Michal Marek <mmarek@...e.cz>, Mike Galbraith <efault@....de>,
"Serge E. Hallyn" <serge.hallyn@...onical.com>,
Jiri Slaby <jslaby@...e.cz>,
Greg Kroah-Hartman <gregkh@...e.de>,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH v9 03/13] seccomp_filter: new mode with configurable
syscall filters
Hi Will,
On Thu, Jun 23, 2011 at 07:36:42PM -0500, Will Drewry wrote:
> This change adds a new seccomp mode which specifies the allowed system
> calls dynamically. When in the new mode (2), all system calls are
> checked against process-defined filters - first by system call number,
> then by a filter string. If an entry exists for a given system call and
> all filter predicates evaluate to true, then the task may proceed.
> Otherwise, the task is killed.
> [...]
> Signed-off-by: Will Drewry <wad@...omium.org>
Thanks for continuing to work on this. I look forward to being able to use
it. :)
Acked-by: Kees Cook <kees.cook@...onical.com>
--
Kees Cook
Ubuntu Security Team
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists