9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] kernel: disallow executing from #| or #d
Date: Tue, 10 May 2022 10:40:41 -0400	[thread overview]
Message-ID: <77567FF86B34A592067F8FA1ADD7F3C6@eigenstate.org> (raw)
In-Reply-To: <28db6450-6d7c-977f-aaff-62f152e79968@posixcafe.org>

Quoth Jacob Moody <moody@mail.posixcafe.org>:
> Hello,
> 
> I noticed that you could execute from #| and #d.
> ex:
> 
> cpu% bind '#|' /n/pipetest
> cpu% /n/pipetest/data1 &
> cpu% echo '#!/bin/rc' >> /n/pipetest/data
> cpu% echo 'echo hello' >> /n/pipetest/data
> cpu% hello
> 
> I believe this would also work for binaries
> if the writer could predict what parts of the binary
> the kernel will want to read. I am inclined to
> block this behavior but would be curious what others
> think. Included is a patch to error on OEXEC opens
> in devdup and devpipe.

I think all files should be the same, as much as
they can be -- we shouldn't necessarily need to
care if we have a pipe or not.


  reply	other threads:[~2022-05-10 14:42 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 [this message]
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
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:
  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=77567FF86B34A592067F8FA1ADD7F3C6@eigenstate.org \
    --to=ori@eigenstate.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).