From: Vasiliy Kulikov <segoon@openwall.com>
To: Andrew Morton <akpm00@gmail.com>
Cc: kernel-hardening@lists.openwall.com,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org, Kees Cook <kees@ubuntu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Valdis.Kletnieks@vt.edu,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: [kernel-hardening] Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
Date: Sat, 1 Oct 2011 00:12:56 +0400 [thread overview]
Message-ID: <20110930201256.GB5173@albatros> (raw)
In-Reply-To: <20110930130353.0da54517.akpm00@gmail.com>
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
http://www.openwall.com - bringing security into open computing environments
WARNING: multiple messages have this Message-ID (diff)
From: Vasiliy Kulikov <segoon@openwall.com>
To: Andrew Morton <akpm00@gmail.com>
Cc: kernel-hardening@lists.openwall.com,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org, Kees Cook <kees@ubuntu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Valdis.Kletnieks@vt.edu,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
Date: Sat, 1 Oct 2011 00:12:56 +0400 [thread overview]
Message-ID: <20110930201256.GB5173@albatros> (raw)
In-Reply-To: <20110930130353.0da54517.akpm00@gmail.com>
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
http://www.openwall.com - bringing security into open computing environments
WARNING: multiple messages have this Message-ID (diff)
From: Vasiliy Kulikov <segoon@openwall.com>
To: Andrew Morton <akpm00@gmail.com>
Cc: kernel-hardening@lists.openwall.com,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org, Kees Cook <kees@ubuntu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Valdis.Kletnieks@vt.edu,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Alan Cox <alan@linux.intel.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] mm: restrict access to /proc/meminfo
Date: Sat, 1 Oct 2011 00:12:56 +0400 [thread overview]
Message-ID: <20110930201256.GB5173@albatros> (raw)
In-Reply-To: <20110930130353.0da54517.akpm00@gmail.com>
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
http://www.openwall.com - bringing security into open computing environments
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-09-30 20:12 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:54 [kernel-hardening] [PATCH 1/2] mm: restrict access to slab files under procfs and sysfs Vasiliy Kulikov
2011-09-27 17:54 ` Vasiliy Kulikov
2011-09-27 17:54 ` Vasiliy Kulikov
2011-09-27 17:56 ` [kernel-hardening] [PATCH 2/2] mm: restrict access to /proc/meminfo Vasiliy Kulikov
2011-09-27 17:56 ` Vasiliy Kulikov
2011-09-27 17:56 ` Vasiliy Kulikov
2011-09-27 18:27 ` [kernel-hardening] " David Rientjes
2011-09-27 18:27 ` David Rientjes
2011-09-27 18:27 ` David Rientjes
2011-09-27 19:14 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-27 19:14 ` Vasiliy Kulikov
2011-09-27 19:14 ` Vasiliy Kulikov
2011-09-27 19:38 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-27 19:38 ` Vasiliy Kulikov
2011-09-27 19:38 ` Vasiliy Kulikov
2011-09-27 20:03 ` [kernel-hardening] " Christoph Lameter
2011-09-27 20:03 ` Christoph Lameter
2011-09-27 20:03 ` Christoph Lameter
2011-09-27 20:33 ` [kernel-hardening] " David Rientjes
2011-09-27 20:33 ` David Rientjes
2011-09-27 20:33 ` David Rientjes
2011-09-27 20:47 ` [kernel-hardening] " Christoph Lameter
2011-09-27 20:47 ` Christoph Lameter
2011-09-27 20:47 ` Christoph Lameter
2011-09-28 20:31 ` [kernel-hardening] " Dave Hansen
2011-09-28 20:31 ` Dave Hansen
2011-09-28 20:31 ` Dave Hansen
2011-09-28 20:52 ` [kernel-hardening] " Alan Cox
2011-09-28 20:52 ` Alan Cox
2011-09-28 20:52 ` Alan Cox
2011-09-29 0:43 ` [kernel-hardening] " Valdis.Kletnieks
2011-09-29 0:43 ` Valdis.Kletnieks
2011-09-29 14:11 ` [kernel-hardening] " Christoph Lameter
2011-09-29 14:11 ` Christoph Lameter
2011-09-29 14:11 ` Christoph Lameter
2011-09-29 16:18 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-29 16:18 ` Vasiliy Kulikov
2011-09-29 16:18 ` Vasiliy Kulikov
2011-09-29 16:30 ` [kernel-hardening] " Dave Hansen
2011-09-29 16:30 ` Dave Hansen
2011-09-29 16:30 ` Dave Hansen
2011-09-29 16:43 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-29 16:43 ` Vasiliy Kulikov
2011-09-29 16:57 ` Valdis.Kletnieks
2011-09-29 16:57 ` Valdis.Kletnieks
2011-09-29 17:25 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-29 17:25 ` Vasiliy Kulikov
2011-09-29 17:28 ` Vasiliy Kulikov
2011-09-29 17:28 ` Vasiliy Kulikov
2011-09-29 17:28 ` Vasiliy Kulikov
2011-09-28 21:46 ` [kernel-hardening] " Andrew Morton
2011-09-28 21:46 ` Andrew Morton
2011-09-28 21:46 ` Andrew Morton
2011-09-30 19:53 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-30 19:53 ` Vasiliy Kulikov
2011-09-30 19:53 ` Vasiliy Kulikov
2011-09-30 20:03 ` [kernel-hardening] " Andrew Morton
2011-09-30 20:03 ` Andrew Morton
2011-09-30 20:03 ` Andrew Morton
2011-09-30 20:12 ` Vasiliy Kulikov [this message]
2011-09-30 20:12 ` Vasiliy Kulikov
2011-09-30 20:12 ` Vasiliy Kulikov
2011-09-30 20:15 ` [kernel-hardening] " Dave Hansen
2011-09-30 20:15 ` Dave Hansen
2011-09-30 20:15 ` Dave Hansen
2011-09-27 18:08 ` [kernel-hardening] Re: [PATCH 1/2] mm: restrict access to slab files under procfs and sysfs Christoph Lameter
2011-09-27 18:08 ` Christoph Lameter
2011-09-27 18:08 ` Christoph Lameter
2011-09-27 19:16 ` [kernel-hardening] " Vasiliy Kulikov
2011-09-27 19:16 ` Vasiliy Kulikov
2011-09-27 19:16 ` Vasiliy Kulikov
2011-09-27 19:35 ` [kernel-hardening] " Christoph Lameter
2011-09-27 19:35 ` Christoph Lameter
2011-09-27 19:35 ` Christoph Lameter
2011-09-27 18:21 ` [kernel-hardening] " David Rientjes
2011-09-27 18:21 ` David Rientjes
2011-09-27 18:21 ` David Rientjes
2011-09-27 20:00 ` [kernel-hardening] " Pekka Enberg
2011-09-27 20:00 ` Pekka Enberg
2011-09-27 20:00 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110930201256.GB5173@albatros \
--to=segoon@openwall.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm00@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=cl@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=kees@ubuntu.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.