[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EB843FF.5080201@zytor.com>
Date: Mon, 07 Nov 2011 12:47:59 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Vasiliy Kulikov <segoon@...nwall.com>
CC: Eric Paris <eparis@...isplace.org>, kernel-hardening@...ts.openwall.com,
Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org,
Alexey Dobriyan <adobriyan@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-security-module@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Re: [PATCH] proc: restrict access to /proc/interrupts
On 11/07/2011 12:11 PM, Vasiliy Kulikov wrote:
>
> My statement was about static files - /proc/{interrupts,meminfo,stat,cpuinfo}.
> They don't change during the system life. /proc/$PID/* files are indeed
> dymanic and the first link in my quoted email was about addition of such
> mount options.
>
You didn't really get my point. There are global nodes which are
dynamic, and more importantly the *set* changes across the system life.
A global policy option is a lot easier to deal with for the vast
majority of users who don't need fine grain control.
-hpa
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.
