From: magma698hfsp273p9f@icebubble.org
To: 9front@9front.org
Subject: Re: [9front] RFNOMNT vs unmount
Date: Mon, 21 Dec 2020 18:51:59 +0000 [thread overview]
Message-ID: <867dpbj8kw.fsf@cmarib.ramside> (raw)
In-Reply-To: <B9BD66E29227BE4F8052086A6A1FD797@eigenstate.org> (ori@eigenstate.org's message of "Sun, 20 Dec 2020 13:52:23 -0800")
ori@eigenstate.org writes:
> Luckily, we have rfork m to prevent new mounts.
> Unluckily, rfork m still allows unmounting,
> which means that if you mount a constructed
> naemspace over /, that can be undone.
What?! Has that flaw been in the kernel since day one?
> Quoth cinap_lenrek@felloff.net:
> Right, and I don't *intend* to allow mounts and arbitrary
> commands in other scripts, but bugs happen and lead to RCE
> or shell escapes.
>
> I see namespaces as something that could be a tool to help
> make those harder to exploit.
I agree w/ori. You can't rely on server application program logic to
enforce security. Sometimes, it helps to have assistance from the
operating system.
next prev parent reply other threads:[~2020-12-21 20:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 20:33 ori
2020-12-20 21:39 ` cinap_lenrek
2020-12-20 21:52 ` ori
2020-12-21 18:51 ` magma698hfsp273p9f [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-21 6:25 [9front] " ori
2020-12-21 15:34 ` [9front] " Xiao-Yong Jin
2020-12-20 19:22 ori
2020-12-20 19:49 ` hiro
2020-12-20 20:32 ` Steve Simon
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=867dpbj8kw.fsf@cmarib.ramside \
--to=magma698hfsp273p9f@icebubble.org \
--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).