From: Daniel Jacobowitz <dan@debian.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Why are exe, cwd, and root priviledged bits of information?
Date: Thu, 7 Nov 2002 11:05:21 -0500 [thread overview]
Message-ID: <20021107160521.GA18270@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0211071052540.8252-100000@rtlab.med.cornell.edu>
On Thu, Nov 07, 2002 at 10:57:06AM -0500, Calin A. Culianu wrote:
>
> In the /prod/PID subset of procfs, why are the exe, cwd, and root symlinks
> considered priviledged information?
>
> Exe is the big one for me, as this one can be usually infered from reading
> /prod/PID/maps. Root I guess can't be inferred in any unpriviledged way,
> and neither can cwd. At any rate.. I am not sure behind the philosophy to
> make these symlinks' destinations priviledged... can someone clarify
> this?
This came up a little while ago. The answer is that maps should be
priviledged also.
For instance:
You can protect a directory by giving its parent directory no read
permissions. The name of the directory is now secret. You don't want
to reveal it in cwd.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-07 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 15:57 Why are exe, cwd, and root priviledged bits of information? Calin A. Culianu
2002-11-07 16:05 ` Daniel Jacobowitz [this message]
2002-11-07 22:16 ` jw schultz
2002-11-07 22:28 ` Daniel Jacobowitz
2002-11-07 22:41 ` Jesse Pollard
2002-11-08 1:55 ` jw schultz
2002-11-08 6:28 ` Rob Landley
2002-11-07 22:44 ` David Wagner
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=20021107160521.GA18270@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.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