From: Charles Forsyth <charles.forsyth@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 22:57:16 +0000 [thread overview]
Message-ID: <CAOw7k5i5Hbw=vLCD1YGo7pbpXSyKMtmu0qboxB1ybX1nQZNGTw@mail.gmail.com> (raw)
In-Reply-To: <7ef5897118148acd265fac9b434f8684@felloff.net>
[-- Attachment #1: Type: text/plain, Size: 408 bytes --]
On 14 February 2016 at 16:38, <cinap_lenrek@felloff.net> wrote:
> i could imagine the filtering being usefull when cpu'ing to foreign
> machines,
> as a server can easily compromize your system when cpu exports your whole
> local namespace
>
You'd still be better off using a custom nsfile to control it, running that
cpu in
a more restricted name space from the start, so leaks are impossible.
[-- Attachment #2: Type: text/html, Size: 791 bytes --]
next prev parent reply other threads:[~2016-02-14 22:57 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
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 [this message]
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='CAOw7k5i5Hbw=vLCD1YGo7pbpXSyKMtmu0qboxB1ybX1nQZNGTw@mail.gmail.com' \
--to=charles.forsyth@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).