[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090112194333.GB23848@one.firstfloor.org>
Date: Mon, 12 Jan 2009 20:43:33 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Valdis.Kletnieks@...edu
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Michael Stone <michael@...top.org>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: RFC: Network privilege separation.
> Yes, the network access part *is* something that should be part of a more
> general interface. Having said that, we currently are lacking a way for a
> *general user* program to say "I'm all set up, and would like to disavow any
> other further resource access (except maybe r/o access as "other" to file
> systems)".
seccomp does exactly that. It's quite obscure, but available in most
linux kernels. Basically it blocks everything except
read/write on already open file descriptors.
I always thought it would be nice if codecs (which tend
to be full of security holes) ran in such jails by default
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists