[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080321151935.6a330536.akpm@linux-foundation.org>
Date: Fri, 21 Mar 2008 15:19:35 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Christoph Lameter <clameter@....com>
Cc: arjan@...radead.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [1/2] vmalloc: Show vmalloced areas via /proc/vmallocinfo
On Thu, 20 Mar 2008 12:22:07 -0700 (PDT)
Christoph Lameter <clameter@....com> wrote:
> On Wed, 19 Mar 2008, Arjan van de Ven wrote:
>
> > > + proc_create("vmallocinfo",S_IWUSR|S_IRUGO, NULL,
> > why should non-root be able to read this? sounds like a security issue (info leak) to me...
What is the security concern here? This objection is rather vague.
> Well I copied from the slabinfo logic (leaking info for slabs is okay?).
>
> Lets restrict it to root then:
>
>
>
> Subject: vmallocinfo: Only allow root to read /proc/vmallocinfo
>
> Change permissions for /proc/vmallocinfo to only allow read
> for root.
That makes the feature somewhat less useful. Let's think this through more
carefully - it is, after all, an unrevokable, unalterable addition to the
kernel ABI.
Arjan, what scenarios are you thinking about?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists