From: FabF <fabian.frederick@skynet.be>
To: Andi Kleen <ak@muc.de>
Cc: viro@parcelfarce.linux.theplanet.co.uk, linux-kernel@vger.kernel.org
Subject: Re: procfs permissions on 2.6.x
Date: Mon, 05 Jul 2004 00:37:22 +0200 [thread overview]
Message-ID: <1088980642.2429.4.camel@localhost.localdomain> (raw)
In-Reply-To: <m34qone7f6.fsf@averell.firstfloor.org>
On Mon, 2004-07-05 at 00:25, Andi Kleen wrote:
> viro@parcelfarce.linux.theplanet.co.uk writes:
> >
> > Why on the earth do we ever want to allow chown/chmod on procfs in the first
> > place?
>
> It's useful to stop other people from reading your environment
> or command line.
We wouldn't need that feature if mods are accurately defined from the
beginning (ie at creation) at that's already the case AFAICS.
FabF
next prev parent reply other threads:[~2004-07-04 22:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2dZjc-7BP-15@gated-at.bofh.it>
[not found] ` <2dZjf-7BP-27@gated-at.bofh.it>
[not found] ` <2dZsQ-7GF-23@gated-at.bofh.it>
[not found] ` <2dZVV-867-33@gated-at.bofh.it>
[not found] ` <2e0oZ-8lm-35@gated-at.bofh.it>
[not found] ` <2emSs-6R8-17@gated-at.bofh.it>
[not found] ` <2enbS-72q-19@gated-at.bofh.it>
[not found] ` <2env9-7li-9@gated-at.bofh.it>
2004-07-04 22:25 ` procfs permissions on 2.6.x Andi Kleen
2004-07-04 22:37 ` FabF [this message]
2004-07-04 23:30 ` Paul Jackson
2004-07-03 20:22 Herbert Poetzl
2004-07-03 20:25 ` Christoph Hellwig
2004-07-03 20:35 ` Andrew Morton
2004-07-03 21:04 ` Christoph Hellwig
2004-07-03 21:35 ` Andrew Morton
2004-07-04 21:35 ` viro
2004-07-04 21:55 ` Andrew Morton
2004-07-04 22:13 ` viro
2004-07-04 22:43 ` Andrew Morton
2004-07-06 3:31 ` Andy Lutomirski
2004-07-05 1:50 ` Clemens Schwaighofer
2004-07-05 1:55 ` viro
2004-07-05 8:05 ` Duncan Sands
2004-07-05 8:14 ` Clemens Schwaighofer
2004-07-04 1:27 ` bert hubert
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=1088980642.2429.4.camel@localhost.localdomain \
--to=fabian.frederick@skynet.be \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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