[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1316024680.4478.61.camel@nimitz>
Date: Wed, 14 Sep 2011 11:24:40 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Vasiliy Kulikov <segoon@...nwall.com>
Cc: kernel-hardening@...ts.openwall.com,
Andrew Morton
<akpm@...ux-foundation.org>,
Cyrill Gorcunov <gorcunov@...il.com>,
Al Viro
<viro@...iv.linux.org.uk>,
Christoph Lameter <cl@...ux-foundation.org>,
Pekka Enberg <penberg@...nel.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 Wed, 2011-09-14 at 19:42 +0400, Vasiliy Kulikov wrote:
> > In other words, I dunno. If we do this in the kernel, can we at least
> > do something like CONFIG_INSECURE to both track these kinds of things
> > and make it easy to get them out of a developer's way?
>
> What do you think about adding your user to the slabinfo's group or
> chmod it - quite the opposite Ubuntu currently does? I think it is more
> generic (e.g. you may chmod 0444 to allow all users to get debug
> information or just 0440 and chgrp admin to allow only trusted users to
> do it) and your local policy doesn't touch the kernel.
That obviously _works_. I'd be happy to ack your patch. As I said,
it's pretty minimally painful, even to folks who care about slabinfo
like me.
-- Dave
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.
