[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 19 Sep 2011 20:55:41 +0100
From: Alan Cox <alan@...ux.intel.com>
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>, 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 15:45:07 -0400
Valdis.Kletnieks@...edu wrote:
> On Mon, 19 Sep 2011 18:46:58 +0400, Vasiliy Kulikov said:
>
> > One note: only to _kernel_ developers. It means it is a strictly
> > debugging feature, which shouldn't be enabled in the production
> > systems.
>
> Until somebody at vendor support says "What does 'cat /proc/slabinfo'
> say?"
>
> Anybody who thinks that debugging tools should be totally disabled on
> "production" systems probably hasn't spent enough time actually
> running production systems.
Agreed - far better it is simply set root only. At that point if you
can read it you've bypassed DAC anyway so either you already control
the box or something like SELinux or SMACK is in the way in which case
*it* can manage extra policy just fine.
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.
