9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] permissions
Date: Wed, 24 Oct 2001 08:44:49 +0000	[thread overview]
Message-ID: <3BD5DEAC.8B73B81@null.net> (raw)
In-Reply-To: <3BD5D457.D28FAE72@zip.com.au>

Matthew Hannigan wrote:
> Is the distinction between x and r for directories
> really that useful?   When does it matter?  I can
> only think of "inbox" type directories.
> I'm still thinking of being able to get rid of the
> 'x' permission on everything.

There is no canonically "right" answer to such a question.
If you think of the permission bits as providing per-file
(or per-entry) information that can be used by some
algorithm that enforces some security policy, then we
need to know the specific policy before being able to
give a specific answer.

It is certain that a process that can read an executable
image can in principle "execute" it by acting as an
interpreter.  Therefore for the "x" bit to be more useful
it needs to grant access to some additional capability.
In the case of a directory file, traditionally "r" and "x"
differ in that one means "can traverse as a pathname
component" while the other means "can read its entries".
These are definitely not the same thing.


  reply	other threads:[~2001-10-24  8:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 14:28 Russ Cox
2001-10-23 20:34 ` Matthew Hannigan
2001-10-24  8:44   ` Douglas A. Gwyn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-10-17  5:35 Benjamin Huntsman
2010-10-17  6:00 ` Skip Tavakkolian
2010-10-17  6:19   ` erik quanstrom
2010-10-17  6:36     ` Benjamin Huntsman
2010-10-17 13:59       ` erik quanstrom
2010-10-17 16:01       ` blstuart
2010-10-17 16:11         ` erik quanstrom
2010-10-17 17:17           ` ron minnich
2010-10-17 18:11         ` Benjamin Huntsman
2010-10-17 18:18           ` erik quanstrom
2010-10-17 19:17             ` blstuart
2010-10-17 19:59               ` Benjamin Huntsman
2010-10-17 20:40                 ` blstuart
2010-10-17 21:22                   ` Benjamin Huntsman
2010-10-17 22:56                     ` erik quanstrom
2010-10-18  9:00                       ` Steve Simon
2010-10-18  9:29                         ` dave.l
2010-10-18  9:34                         ` Bruce Ellis
2010-10-18 11:07                         ` Dave Eckhardt
2010-10-18 11:11                           ` Bruce Ellis
2010-10-17 22:58                     ` blstuart
2010-10-19 18:18                 ` Nathaniel W Filardo
2010-10-17 23:00               ` erik quanstrom
2001-10-18 14:00 Russ Cox
2001-10-18 14:12 ` Lucio De Re
2001-10-18 13:56 Lucio De Re

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=3BD5DEAC.8B73B81@null.net \
    --to=dagwyn@null.net \
    --cc=9fans@cse.psu.edu \
    /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).