From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: Rik van Riel <riel@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/7] procfs privacy: tasks/processes lookup
Date: Mon, 18 Apr 2005 21:59:30 +0200 [thread overview]
Message-ID: <1113854370.17341.115.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0504181523440.11251@chimarrao.boston.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
El lun, 18-04-2005 a las 15:24 -0400, Rik van Riel escribió:
> This looks like a very bad default to me!
>
> Your patch would force people to run system monitoring
> applications as root, because otherwise they cannot get
> some of the information they can get now. Forcing that
> these applications run with root rights is a security
> risk, not a benefit...
Right, that's why I would say "fall back to the config. option"
behavior, trusting in a certain user group defined in configuration-time
or via sysctl, or just keeping it simple as it's right now, split up so
anyone can decide what to apply and what shouldn't be applied.
Cheers,
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-18 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 18:46 [PATCH 2/7] procfs privacy: tasks/processes lookup Lorenzo Hernández García-Hierro
2005-04-18 19:24 ` Rik van Riel
2005-04-18 19:59 ` Lorenzo Hernández García-Hierro [this message]
2005-04-20 19:41 ` Rene Scharfe
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=1113854370.17341.115.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/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