Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 1 Oct 2011 00:12:56 +0400
From: Vasiliy Kulikov <>
To: Andrew Morton <>
	Christoph Lameter <>,
	Pekka Enberg <>, Matt Mackall <>,, Kees Cook <>,
	Dave Hansen <>,,
	Linus Torvalds <>,
	David Rientjes <>,
	Alan Cox <>,,
	Andrew Morton <>
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo

On Fri, Sep 30, 2011 at 13:03 -0700, Andrew Morton wrote:
> meminfo has been around for a very long time and is a convenient and
> centralised point for collecting memory data.  There will be a large
> number of apps/scripts/tools out there which use it.  Many of these
> won't even be available to us.
> All of which makes it very hard for us to predict how much breakage we
> will cause.
> > If we care about (2), we should pass non-zero counters, but imagine some
> > default values, which will result in sane processes numbers.  But it
> > might depend on specific applications, I'm not aware whether (2) is
> > real.
> > 
> > 
> > Other ideas?
> echo "chmod 0400 /proc/meminfo" >> /etc/rc.local

How will it help to fix apps' dependencies on meminfo?

Vasiliy Kulikov - bringing security into open computing environments

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.