[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110928144614.38591e97.akpm00@gmail.com>
Date: Wed, 28 Sep 2011 14:46:14 -0700
From: Andrew Morton <akpm00@...il.com>
To: Vasiliy Kulikov <segoon@...nwall.com>
Cc: kernel-hardening@...ts.openwall.com, Christoph Lameter
<cl@...ux-foundation.org>, Pekka Enberg <penberg@...nel.org>, Matt Mackall
<mpm@...enic.com>, linux-mm@...ck.org, Kees Cook <kees@...ntu.com>, Dave
Hansen <dave@...ux.vnet.ibm.com>, Valdis.Kletnieks@...edu, Linus Torvalds
<torvalds@...ux-foundation.org>, David Rientjes <rientjes@...gle.com>, Alan
Cox <alan@...ux.intel.com>, linux-kernel@...r.kernel.org, Andrew Morton
<akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
On Tue, 27 Sep 2011 23:38:10 +0400
Vasiliy Kulikov <segoon@...nwall.com> wrote:
> On Tue, Sep 27, 2011 at 21:56 +0400, Vasiliy Kulikov wrote:
> > /proc/meminfo stores information related to memory pages usage, which
> > may be used to monitor the number of objects in specific caches (and/or
> > the changes of these numbers). This might reveal private information
> > similar to /proc/slabinfo infoleaks. To remove the infoleak, just
> > restrict meminfo to root. If it is used by unprivileged daemons,
> > meminfo permissions can be altered the same way as slabinfo:
> >
> > groupadd meminfo
> > usermod -a -G meminfo $MONITOR_USER
> > chmod g+r /proc/meminfo
> > chgrp meminfo /proc/meminfo
>
> Just to make it clear: since this patch breaks "free", I don't propose
> it anymore.
It will break top(1) too. It isn't my favoritest-ever patch :)
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.
