From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Cc: Richard Miller <9fans@hamnavoe.com>
Subject: Re: [9fans] `test -x` returns wrong results for directories
Date: Mon, 8 Jun 2020 03:20:09 +0100 [thread overview]
Message-ID: <CAOw7k5g0yHxzx890_KHxtbZMheSgcf-05npc=8o6t_73RcQmbg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5gqS4SjfehkapD37CsXkUMdBzu7COxON-Ke0seRF-0FHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
I see I'd misapplied the rule in walk(5) so fossil is fine. It has to do
with searching from . when you are there, which makes sense, not when
entering the directory from its parent,
so ignore that part of my earlier post.
On Mon, Jun 8, 2020 at 3:13 AM Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> "search" is exactly the wrong word for what this bit does, because if you
>> don't have "search" permission, the one thing you can still do is look at
>> the names.
>
>
> in ramfs, but that's a bug that no-one had noticed
>
> On Mon, Jun 8, 2020 at 3:05 AM <ori@eigenstate.org> wrote:
>
>> >>> So, cd'ing into a directory withut +x leads
>> >>> to an inescapabler trap.
>> >> ...
>> >> fossil just moved up another notch in my estimation because directory
>> search restriction is so broken.
>> >
>> > ori@eigenstate.org, what version of fossil were your experiments done
>> on?
>> > My observations are different:
>> >
>> > term% mkdir -p d/a/b
>> > term% touch d/x
>> > term% chmod -x d
>> > term% ls -ld d
>> > d-rw-r--r-- M 12 miller miller 0 Jun 7 16:38 d
>> > term% cd d
>> > term% cd ..
>> > term% ls d
>> > d/a
>> > d/x
>> > term%
>> >
>> > No trap that I can see here.
>>
>> cwfs, but -- yeah, it's enforced inconsistently across
>> different file systems. (of course).
>>
>>
>> ------------------------------------------
>> 9fans: 9fans
>> Permalink:
>> https://9fans.topicbox.com/groups/9fans/Tdd7a9b1b32d01f54-M9cf36356f4d9761339774af6
>> Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
>>
>
[-- Attachment #2: Type: text/html, Size: 2785 bytes --]
next prev parent reply other threads:[~2020-06-08 2:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 12:45 Ethan Gardener
2020-06-05 19:22 ` [9fans] " Richard Miller
2020-06-06 6:36 ` Ethan Gardener
2020-06-06 12:11 ` Alexander Kapshuk
2020-06-06 13:25 ` Charles Forsyth
2020-06-07 13:56 ` Ethan Gardener
2020-06-06 21:13 ` ori
2020-06-07 14:48 ` Ethan Gardener
2020-06-07 15:41 ` Richard Miller
2020-06-08 2:04 ` ori
2020-06-08 2:13 ` Charles Forsyth
2020-06-08 2:20 ` Charles Forsyth [this message]
2020-06-09 10:50 ` Ethan Gardener
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='CAOw7k5g0yHxzx890_KHxtbZMheSgcf-05npc=8o6t_73RcQmbg@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
--cc=9fans@hamnavoe.com \
/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).