9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] Unmount to remove sharp devices.
Date: Wed, 4 May 2022 12:15:54 -0400	[thread overview]
Message-ID: <083AFE4C-A6CF-4926-BCE6-DD97DE0B4915@stanleylieber.com> (raw)
In-Reply-To: <FBF70FE6D65D7182A5EB87FB180CED05@eigenstate.org>

this is very welcome.

one problem with getting rid of mounts and binds is programs that use mounts and binds.

sl

> On May 4, 2022, at 11:32 AM, ori@eigenstate.org wrote:
> 
> Quoth Jacob Moody <moody@mail.posixcafe.org>:
>> Hello,
>> 
>> This patch allows processes to unmount sharp devices to prevent itself and its children from accessing
>> them. This is implemented through an internal rework of how RFNOMNT works, making RFNOMNT a special
>> case of setting disallowed devices. To replicate the mount blocking functionality of RFNOMNT a special
>> case is given for blocking devmnt, which also blocks the process and its children from making any mount
>> calls.
>> 
>> If everything passes the sniff test I can commit these changes. Diff is here: http://okturing.com/src/13574/body and included
>> below.
>> 
>> Thanks,
>> moody
>> 
> 
> also -- are there places that you want to take
> advantage of this within the system? It'd be
> good to use the feature, rather than just having
> it sit around.
> 
> git/serve? rc-httpd? maybe some other daemons
> could use some sandboxing.
> 
> 


  reply	other threads:[~2022-05-04 16:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04 14:09 Jacob Moody
2022-05-04 15:05 ` ori
2022-05-04 15:31 ` ori
2022-05-04 16:15   ` Stanley Lieber [this message]
2022-05-04 17:41   ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-04 17:55     ` Jacob Moody
2022-05-05  1:59       ` Alex Musolino
2022-05-05 16:07         ` Jacob Moody
2022-05-08  2:55           ` Jacob Moody
2022-05-11 14:47             ` Jacob Moody
2022-05-11 16:11               ` Stanley Lieber
2022-05-12  4:29                 ` Jacob Moody
2022-05-12  3:18             ` ori
2022-05-12  5:10               ` Jacob Moody
2022-05-12 14:21                 ` ori
2022-05-23  5:42                   ` Jacob Moody
2022-05-23 17:06                     ` cinap_lenrek
2022-05-23 17:37                       ` Jacob Moody
2022-05-25 19:03                         ` Jacob Moody
2022-05-25 20:53                           ` hiro
2022-05-25 21:20                             ` Jacob Moody
2022-05-26  5:55                               ` Jacob Moody
2022-05-26 23:36                                 ` unobe
2022-05-27  0:33                                   ` Jacob Moody
2022-05-27  3:25                                     ` unobe
2022-05-26  3:13                             ` ori
2022-05-27  1:11                           ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-05-27  2:25                             ` Frank D. Engel, Jr.

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=083AFE4C-A6CF-4926-BCE6-DD97DE0B4915@stanleylieber.com \
    --to=sl@stanleylieber.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).