From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: General flags to turn things off (getrandom, pid lookup, etc) Date: Sat, 26 Jul 2014 12:48:48 -0700 Message-ID: <87egx7dhpb.fsf@x220.int.ebiederm.org> References: <20140725223550.3153f436@alan.etchedpixels.co.uk> Mime-Version: 1.0 Content-Type: text/plain Cc: One Thousand Gnomes , Julien Tinnes , David Drysdale , Al Viro , Paolo Bonzini , LSM List , Greg Kroah-Hartman , Paul Moore , James Morris , Linux API , Meredydd Luff , Christoph Hellwig , "linux-kernel\@vger.kernel.org" , Kees Cook , "Theodore Ts'o" , Henrique de Moraes Holschuh , linux-crypto@vger.kernel.org To: Andy Lutomirski Return-path: In-Reply-To: (Andy Lutomirski's message of "Fri, 25 Jul 2014 14:41:47 -0700") Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org Andy Lutomirski writes: > On Fri, Jul 25, 2014 at 2:35 PM, One Thousand Gnomes > wrote: >> On Fri, 25 Jul 2014 11:30:48 -0700 >> Andy Lutomirski wrote: >> >>> [new thread because this sort of combines two threads] >>> >>> There is recent interest in having a way to turn generally-available >>> kernel features off. Maybe we should add a good one so we can stop >>> bikeshedding and avoid proliferating dumb interfaces. >> >> We sort of have one. It's called capable(). Just needs extending to cover >> anything else you care about, and probably all the numeric constants >> replacing with textual names. The big difference is capable only subdivides roots powers (aka things most applications should not have). When we start talking about things that things that are safe for most applications capable is probably not the right tool for the job. A much closer match is the personality system call. Look at setarch to see how it is used. My biggest concern with personality is there are only 32bits to play with. Still I expect what you want may be a sandbox personality, that disables everything that could possibly be a problem (including access to the personality syscall). Eric