linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Grant Miner <mine0057@mrs.umn.edu>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: The x Bit Problem
Date: Fri, 05 Dec 2003 15:44:37 +0300	[thread overview]
Message-ID: <3FD07DB5.6090708@namesys.com> (raw)
In-Reply-To: <3FD01679.3040007@mrs.umn.edu>

Grant Miner wrote:

> An interesting thing I discovered is that Windows simply ignores the 
> 'x' bit (I should say the Windows equivalent of the 'x' bit, called 
> "traverse folder / execute file"), but there is a policy setting that 
> overrides this attribute.
>
> I know users get tripped up on this a lot in Unix, like when they 
> don't understand why the webserver can't read their public_html 
> directory.  It might be a good option for Linux.
>
>
>
The right solution is to have a separate readdir permission, so that a 
file-directory can be not executable but be listable, and vice-versa.  
The problem comes from overloading the bit and also changing whether 
objects can be simultaneously files and directories.

-- 
Hans



      parent reply	other threads:[~2003-12-05 12:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16333.14692.61778.304155@pc7.dolda2000.com>
     [not found] ` <3FCD47C4.50500@ninja.dynup.net>
     [not found]   ` <3FCE39B8.20307@namesys.com>
     [not found]     ` <16334.15412.686909.927196@laputa.namesys.com>
     [not found]       ` <1070580817.8344.140.camel@arabia.home.lan>
     [not found]         ` <3FD00086.90607@ninja.dynup.net>
2003-12-05  5:24           ` Grant Miner
2003-12-05  8:07             ` Bob
2003-12-05 12:30               ` Tomasz Rola
2003-12-05 14:04                 ` Tomasz Rola
2003-12-05 12:44             ` Hans Reiser [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=3FD07DB5.6090708@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mine0057@mrs.umn.edu \
    --cc=reiserfs-list@namesys.com \
    --subject='Re: The x Bit Problem' \
    /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

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