From: Ray Olszewski <ray@comarre.com>
To: <linux-kernel@vger.kernel.org>
Subject: RE: reading links in proc - permission denied
Date: Sat, 14 Jun 2003 14:10:12 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20030614140335.01fc2260@celine> (raw)
In-Reply-To: <000b01c332b7$44c68250$1403a8c0@sc.tlinx.org>
I am unclear what purpose the long rant about "[p]erfect capitalistic
system" handling of software bugs has to do with an operating system and
applications that most of get for free, so I'll skip that part.
What governs access to a file is ownership and permissions on the file
itself, not on symlinks to it (which are customarily lrwxrwxrwx on Linux
filesystems). This is not mysterious. It's just old-hat Unix.
At 01:55 PM 6/14/2003 -0700, linda w. wrote:
> > -----Original Message-----
> > From: hurtta@leija.mh.fmi.fi [mailto:hurtta@leija.mh.fmi.fi]
> > Are you sure that 'top' uses that 'exe' ?
>---
> Not at all...in fact was told it doesn't. Apparently, though,
>the listed permissions on the links are arbitrary and the system
>fairly well ignores them.
>
> I vaguely remember someone once saying that even if a symlink
>had permissions lrxw------, it could still be used by group and
>others. I don't know if that was or is still true -- certainly doesn't
>seem consistent, but when dealing with computer systems made by
>many different humans, inconsistency seems inevitable -- even when
>made by 1 human, that person can be inconsistent over time.
>
> And people wonder why computer security is so hard to 'get right'.
[rest deleted]
next prev parent reply other threads:[~2003-06-14 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200306141905.h5EJ57mE024740@leija.fmi.fi>
2003-06-14 20:55 ` reading links in proc - permission denied linda w.
2003-06-14 21:10 ` Ray Olszewski [this message]
2003-06-14 22:09 ` root
2003-06-06 2:03 Albert Cahalan
2003-06-06 5:45 ` linda w.
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 3:12 linda w.
2003-06-04 18:59 linda w.
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=5.1.0.14.1.20030614140335.01fc2260@celine \
--to=ray@comarre.com \
--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;
as well as URLs for NNTP newsgroup(s).