From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] kernel: disallow executing from #| or #d
Date: Wed, 11 May 2022 11:32:31 -0500 [thread overview]
Message-ID: <2248A216-6C8C-4C58-AD4A-5D4D2BAAED14@gmail.com> (raw)
In-Reply-To: <c868d55b-2493-db66-740b-17e606a3b99a@posixcafe.org>
On May 11, 2022 1:31:27 AM CDT, Jacob Moody <moody@mail.posixcafe.org> wrote:
>Requiring +x set, then preventing +x from being set
>is just a roundabout way of disabling opening with OEXEC, why
>not just do that?
I'm confused why devpipe allows wstat.
The roundabout way is more general,
checking read/write permissions as well.
The permission info should line up with how a dev allows permissions,
and making open dependent on what the mode is actually set to
would make the info and the behavior always line up.
It might be as easy as a bitwise or.
I'll hack up something later tonight.
If we don't decide on that route,
then devpipe should disallow wstat.
>RFNOMNT does not remove access to #|, #d, #e, #c, or #p
That's what I get for only reading the man page without testing.
Thanks,
Amavect
next prev parent reply other threads:[~2022-05-11 16:34 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 [this message]
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=2248A216-6C8C-4C58-AD4A-5D4D2BAAED14@gmail.com \
--to=amavect@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).