From: Prof Brucee <prof.brucee@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bug in exportfs
Date: Sun, 14 Feb 2016 13:00:54 +1100 [thread overview]
Message-ID: <CAJDwFdhO=eyicMJT9zuwqYe0_aZ+Bg__eAT2jp4NggTicSdZWw@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5gMrWbuoZmfaurN5dwt7vHaLOMj5X2ck1oJ7wu_XTg+YA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Totally agree. I've never needed exportfs filtering. It's not in the patent.
On 14/02/2016 1:27 AM, "Charles Forsyth" <charles.forsyth@gmail.com> wrote:
>
> On 22 December 2015 at 10:02, arisawa <arisawa@ar.aichi-u.ac.jp> wrote:
>
>>
>> The difficulty is in the pattern matching rule.
>> If we want to export only /usr/glenda, then the pattern matching filer
>> must pass
>> /usr
>> /usr/glenda
>> and must not pass
>> /usr/
>>
>
> I really wonder about the pattern-matching code being there at all.
> Without it, exportfs is constrained by the authenticated user's
> permissions, within the exported name space,
> and that's enforced by the operating system (system calls).
> To export only /usr/glenda, I'd build a name space that has only
> /usr/glenda in it, and export that.
>
> The read-only option is enforced by exportfs itself, but at the 9P level:
> it's not too hard to enumerate
> the messages and options that do not cause modifications and reject all
> others (although exportfs wasn't updated to include an
> option added later to open). Still, that can be got right once for all by
> exportfs.
>
[-- Attachment #2: Type: text/html, Size: 1939 bytes --]
next prev parent reply other threads:[~2016-02-14 2:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 23:31 arisawa
2015-12-17 11:40 ` Peter Hull
2015-12-17 13:05 ` arisawa
2015-12-22 9:25 ` Peter Hull
2015-12-22 10:02 ` arisawa
2016-02-13 14:26 ` Charles Forsyth
2016-02-14 2:00 ` Prof Brucee [this message]
2016-02-14 10:27 ` hiro
2016-02-14 12:21 ` Charles Forsyth
2016-02-14 12:33 ` Charles Forsyth
2016-02-14 16:38 ` cinap_lenrek
2016-02-14 22:57 ` Charles Forsyth
2016-02-15 1:05 ` arisawa
2016-02-15 6:12 ` Bruce Ellis
2016-02-15 10:34 ` Charles Forsyth
2016-02-15 10:55 ` lucio
2016-02-15 12:08 ` Charles Forsyth
2016-02-15 12:13 ` Brantley Coile
2016-02-15 15:05 ` lucio
2016-02-15 15:24 ` erik quanstrom
2016-02-15 12:44 ` lucio
2016-02-15 12:48 ` Charles Forsyth
2016-02-15 14:03 ` lucio
2016-02-15 15:38 ` erik quanstrom
2016-02-15 15:56 ` Skip Tavakkolian
2016-02-15 12:18 ` Charles Forsyth
2016-02-15 15:30 ` erik quanstrom
2016-02-15 23:32 ` Charles Forsyth
2016-02-19 14:12 ` Charles Forsyth
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='CAJDwFdhO=eyicMJT9zuwqYe0_aZ+Bg__eAT2jp4NggTicSdZWw@mail.gmail.com' \
--to=prof.brucee@gmail.com \
--cc=9fans@9fans.net \
/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).