From: daw@mozart.cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: Why are exe, cwd, and root priviledged bits of information?
Date: 7 Nov 2002 22:44:09 GMT [thread overview]
Message-ID: <aqeqbp$hgi$1@abraham.cs.berkeley.edu> (raw)
In-Reply-To: 20021107221615.GA2249@pegasys.ws
jw schultz wrote:
>On Thu, Nov 07, 2002 at 11:05:21AM -0500, Daniel Jacobowitz wrote:
>> 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 is correct in that the issue came up recently. He
>gives _his_ answer above. If you believe in security
>through obscurity you will agree with him.
Huh? This has nothing to do with security through obscurity.
This has to do with the Unix permissions model. /proc/pid probably
shouldn't leak information that would otherwise be kept confidential in the
standard Unix permissions model (principle of least surprise, etc.).
>I will agree that there should be no real reason to need
>access to this information.
They why is it allowed? Allowing something that noone needs and
that breaks most people's intuitions of how security will work seems
like a pretty questionable idea.
prev parent reply other threads:[~2002-11-07 22:55 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
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 [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='aqeqbp$hgi$1@abraham.cs.berkeley.edu' \
--to=daw@mozart.cs.berkeley.edu \
--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