9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] kernel: disallow executing from #| or #d
Date: Wed, 11 May 2022 10:50:44 -0600	[thread overview]
Message-ID: <004c4a6d-957d-1623-9b5d-2f6bbf940f24@posixcafe.org> (raw)
In-Reply-To: <2248A216-6C8C-4C58-AD4A-5D4D2BAAED14@gmail.com>

On 5/11/22 10:32, Amavect wrote:
> If we don't decide on that route,
> then devpipe should disallow wstat.

The roundabout way of checking for permission bits was
my first pass at removing this capability. I am much
more in favor of just disabling wstat for devpipe
personally. If you did want to make one end
of a pipe read only or write only, doing it through
wstat feels obtuse due to the attach semantics.

>> RFNOMNT does not remove access to #|, #d, #e, #c, or #p
> That's what I get for only reading the man page without testing.

Yeah the man page should not lie, how's this instead?


diff 51669adf2446385b38bab4efcb4133c19e9be806 uncommitted
--- a//sys/man/2/fork
+++ b//sys/man/2/fork
@@ -70,9 +70,16 @@
 If set, subsequent mounts into the new name space and dereferencing
-of pathnames starting with
+of most pathnames starting with
 .B #
-are disallowed.
+are disallowed. Specifically
+.IR pipe(3) ,
+.IR dup(3) ,
+.IR env(3) ,
+.IR cons(3) ,
+.IR proc(3)
+are still permitted.
 If set, the environment variables are copied;

  reply	other threads:[~2022-05-11 16:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  6:40 Jacob Moody
2022-05-10 14:40 ` ori
2022-05-10 16:34   ` Jacob Moody
2022-05-10 19:59     ` Amavect
2022-05-10 22:47       ` Jacob Moody
2022-05-11  4:21         ` Amavect
2022-05-11  6:31           ` Jacob Moody
2022-05-11 16:32             ` Amavect
2022-05-11 16:50               ` Jacob Moody [this message]
2022-05-15  2:43                 ` Amavect
2022-05-15 15:26                   ` Amavect
2022-05-15 16:28                     ` Jacob Moody
2022-05-10 20:52 ` [9front] " Anthony Martin

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=004c4a6d-957d-1623-9b5d-2f6bbf940f24@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.org \
    --subject='Re: [9front] [PATCH] kernel: disallow executing from #| or #d' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).