linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: root@mauve.demon.co.uk
To: linux-newbie@tlinx.org (linda w.)
Cc: linux-kernel@vger.kernel.org
Subject: Re: reading links in proc - permission denied
Date: Sat, 14 Jun 2003 23:09:40 +0100 (BST)	[thread overview]
Message-ID: <200306142209.XAA17516@mauve.demon.co.uk> (raw)
In-Reply-To: <000b01c332b7$44c68250$1403a8c0@sc.tlinx.org> from "linda w." at Jun 14, 2003 01:55:21 PM

> ---
> 	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

man symlink
...
       The permissions of a symbolic  link  are  irrelevant;  the
       ownership  is  ignored  when  following  the  link, but is
       checked when removal or renaming of the link is  requested
       and the link is in a directory with the sticky bit set.

In short, the permissions of the file being linked to are important.

  parent reply	other threads:[~2003-06-14 22:00 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
2003-06-14 22:09   ` root [this message]
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=200306142209.XAA17516@mauve.demon.co.uk \
    --to=root@mauve.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-newbie@tlinx.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).