mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alan Curry" <pacman-kernel@manson.clss.net>
To: davej@redhat.com (Dave Jones)
Cc: lorenzo@gnu.org (Lorenzo Hernández García-Hierro),
	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:38:18 -0500 (EST)	[thread overview]
Message-ID: <20050418203818.22843.qmail@manson.clss.net> (raw)
In-Reply-To: <20050418190552.GA26322@redhat.com> from "Dave Jones" at Apr 18, 2005 03:05:52 PM

Dave Jones writes the following:
>
>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:

[snip]
> >  - /proc/uptime
       ^^^^^^^^^^^^ ?!
[snip]

> >  - /proc/cpuinfo
>
>This is utterly absurd. You can find out anything thats in /proc/cpuinfo
>by calling cpuid instructions yourself.

Also it's the backend of glibc's get_nprocs(), also known as
sysconf(_SC_NPROCESSORS_ONLN), a documented interface whose users are
probably not expecting it to suddenly become restricted to root.

>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.

Like uptime(1), a command which has existed basically unchanged since 3.0BSD
(note to observers: if you think that's a funny way of writing "FreeBSD 3.0",
you're off by at least a decade and a half).


      parent reply	other threads:[~2005-04-18 20:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 18:46 Lorenzo Hernández García-Hierro
2005-04-18 19:05 ` Dave Jones
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 [this message]

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=20050418203818.22843.qmail@manson.clss.net \
    --to=pacman-kernel@manson.clss.net \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®