From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fallback.mail.elte.hu (fallback.mail.elte.hu [157.181.151.13]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 9DAA5B6F80 for ; Thu, 12 May 2011 20:50:48 +1000 (EST) Received: from mx3.mail.elte.hu ([157.181.1.138]) by fallback.mail.elte.hu with esmtp (Exim) id 1QKTTe-0004SO-Gf from for ; Thu, 12 May 2011 12:50:42 +0200 Date: Thu, 12 May 2011 12:49:16 +0200 From: Ingo Molnar To: Kees Cook Subject: Re: [PATCH 3/5] v2 seccomp_filters: Enable ftrace-based system call filtering Message-ID: <20110512104916.GJ9937@elte.hu> References: <1304017638.18763.205.camel@gandalf.stny.rr.com> <1305169376-2363-1-git-send-email-wad@chromium.org> <20110512074850.GA9937@elte.hu> <20110512092424.GO28888@outflux.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20110512092424.GO28888@outflux.net> Cc: linux-mips@linux-mips.org, linux-sh@vger.kernel.org, Peter Zijlstra , Frederic Weisbecker , Heiko Carstens , Oleg Nesterov , David Howells , Paul Mackerras , Eric Paris , "H. Peter Anvin" , sparclinux@vger.kernel.org, Jiri Slaby , linux-s390@vger.kernel.org, Russell King , x86@kernel.org, jmorris@namei.org, Linus Torvalds , Ingo Molnar , linux-arm-kernel@lists.infradead.org, "Serge E. Hallyn" , Peter Zijlstra , microblaze-uclinux@itee.uq.edu.au, Steven Rostedt , Martin Schwidefsky , Thomas Gleixner , Roland McGrath , Michal Marek , Michal Simek , Will Drewry , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, Ralf Baechle , Paul Mundt , Tejun Heo , linux390@de.ibm.com, Andrew Morton , agl@chromium.org, "David S. Miller" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , * Kees Cook wrote: > Hi, > > On Thu, May 12, 2011 at 09:48:50AM +0200, Ingo Molnar wrote: > > 1) We already have a specific ABI for this: you can set filters for events via > > an event fd. > > > > Why not extend that mechanism instead and improve *both* your sandboxing > > bits and the events code? This new seccomp code has a lot more > > to do with trace event filters than the minimal old seccomp code ... > > Would this require privileges to get the event fd to start with? [...] No special privileges with the default perf_events_paranoid value. > [...] If so, I would prefer to avoid that, since using prctl() as shown in > the patch set won't require any privs. and we could also explicitly allow syscall events without any privileges, regardless of the setting of 'perf_events_paranoid' config value. Obviously a sandboxing host process wants to run with as low privileges as it can. Thanks, Ingo