[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1109191502040.13103@router.home>
Date: Mon, 19 Sep 2011 15:02:34 -0500 (CDT)
From: Christoph Lameter <cl@...two.org>
To: Valdis.Kletnieks@...edu
cc: Vasiliy Kulikov <segoon@...nwall.com>,
Pekka Enberg <penberg@...helsinki.fi>,
Andrew Morton <akpm@...ux-foundation.org>,
kernel-hardening@...ts.openwall.com, Kees Cook <kees@...ntu.com>,
Cyrill Gorcunov <gorcunov@...il.com>, Al Viro <viro@...iv.linux.org.uk>,
Christoph Lameter <cl@...ux-foundation.org>, Matt Mackall <mpm@...enic.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Dan Rosenberg <drosenberg@...curity.com>, Theodore Tso <tytso@....edu>,
Alan Cox <alan@...ux.intel.com>, Jesper Juhl <jj@...osbits.net>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Re: [RFC PATCH 2/2] mm: restrict access to
/proc/slabinfo
On Mon, 19 Sep 2011, Valdis.Kletnieks@...edu wrote:
> On Mon, 19 Sep 2011 12:51:10 CDT, Christoph Lameter said:
>
> > IMHO a restriction of access to slab statistics is reasonable in a
> > hardened environment. Make it dependent on CONFIG_SECURITY or some such
> > thing?
>
> Probably need to invent a separate Kconfig variable - CONFIG_SECURITY
> is probably a way-too-big hammer for this nail. I can see lots of systems
> that want to enable that, but won't want to tighten access to slab.
There is already CONFIG_SECURITY_DMESG_RESTRICT. Generalize that setting
to include all sorts of other kernel statistics?
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
