linux-kernel - Re: [RFC 1/1] seccomp: Add bitmask of allowed system calls.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090508091912.GB3559@elte.hu>
Date:	Fri, 8 May 2009 11:19:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Tom Zanussi <tzanussi@...il.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Adam Langley <agl@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	linux-kernel@...r.kernel.org, markus@...gle.com
Subject: Re: [RFC 1/1] seccomp: Add bitmask of allowed system calls.


* Tom Zanussi <tzanussi@...il.com> wrote:

> I guess it would be easier for seccomp to make use of the 
> filtering and reuse the syscall tracing facility if we added 
> filtering to the syscall tracer first.  It would be useful to do 
> for the syscall tracer anyway, regardless of whether it (or 
> something similar) ended up being used by seccomp.
> 
> Frederic, did you have any plans for that?  If not, I can take a 
> look when I get the chance...

Doing that would be very nice and useful indeed.

	Ingo
--
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/