From: Xiao-Yong Jin <meta.jxy@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] RFNOMNT vs unmount
Date: Mon, 21 Dec 2020 09:34:24 -0600 [thread overview]
Message-ID: <78F17539-7073-46C5-9575-3767CB994C63@gmail.com> (raw)
In-Reply-To: <28EAA3C5D0E2A371721F57EF38F171A4@eigenstate.org>
> On Dec 21, 2020, at 12:25 AM, ori@eigenstate.org wrote:
>
> My goal is to restrict the impact of a compromised process;
> for example, if I were inappropriately escaping paths in
> shithub, and someone were able to inject a shell command,
> I would like the viewer to be unable to access the user
> home directories.
It looks like the responsibility of tcp80 and ftpd to prepare a
proper clean name space, RFCNAMEG?
next prev parent reply other threads:[~2020-12-21 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 19:22 ori
2020-12-20 19:49 ` hiro
2020-12-20 20:32 ` Steve Simon
2020-12-20 23:51 ` [9front] " Anthony Martin
2020-12-21 6:25 ` ori
2020-12-21 15:34 ` Xiao-Yong Jin [this message]
2020-12-20 20:33 [9front] " ori
2020-12-20 21:39 ` cinap_lenrek
2020-12-20 21:52 ` ori
2020-12-21 18:51 ` magma698hfsp273p9f
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=78F17539-7073-46C5-9575-3767CB994C63@gmail.com \
--to=meta.jxy@gmail.com \
--cc=9front@9front.org \
/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).