From: Dave Jones <davej@redhat.com>
To: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/7] procfs privacy: misc. entries
Date: Mon, 18 Apr 2005 15:05:52 -0400 [thread overview]
Message-ID: <20050418190552.GA26322@redhat.com> (raw)
In-Reply-To: <1113850012.17341.71.camel@localhost.localdomain>
On Mon, Apr 18, 2005 at 08:46:52PM +0200, Lorenzo Hernández García-Hierro wrote:
> This patch changes the permissions of the following procfs entries to
> restrict non-root users from accessing them:
>
> - /proc/devices
> - /proc/cmdline
> - /proc/version
> - /proc/uptime
> - /proc/cpuinfo
This is utterly absurd. You can find out anything thats in /proc/cpuinfo
by calling cpuid instructions yourself.
Please enlighten me as to what security gains we achieve
by not allowing users to see this ?
Restricting lots of the other files are equally absurd.
I'd also be very surprised if various random bits of userspace
broke subtley due to this nonsense.
Dave
next prev parent reply other threads:[~2005-04-18 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 18:46 [PATCH 3/7] procfs privacy: misc. entries Lorenzo Hernández García-Hierro
2005-04-18 19:05 ` Dave Jones [this message]
2005-04-18 19:39 ` Lorenzo Hernández García-Hierro
2005-04-18 21:33 ` David Wagner
2005-04-18 20:38 ` Alan Curry
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=20050418190552.GA26322@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@gnu.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.