From: Michael Sammler <msammler@mpi-sws.org>
To: "Stephen Röttger" <sroettger@google.com>
Cc: Kees Cook <keescook@chromium.org>,
linux-api@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linuxram@us.ibm.com, luto@amacapital.net, wad@chromium.org
Subject: Re: [RFC PATCH] seccomp: Add protection keys into seccomp_data
Date: Mon, 14 Nov 2022 20:16:07 -0800 (PST) [thread overview]
Message-ID: <0a643215-03ce-4388-bd1a-301dcab87c41@mpi-sws.org> (raw)
In-Reply-To: <CAEAAPHZrMDGsAnZM=GC0bu5WpGvXaDakJBq-WDkW06aDc7_68w@mail.gmail.com>
> We're currently working on a feature in chromium that uses pkeys for
> in-process isolation. Being able to use the pkey state in the seccomp
> filter would be pretty useful for this. For example, it would allow
> us to enforce that no code outside the isolated thread would ever
> map/mprotect executable memory.
> We can probably do something similar by adding instruction pointer
> checks to the seccomp filter, but that feels quite hacky and this
> feature would make a much nicer implementation.
>
> Are there any plans to make a version 2 of this patch?
Thanks for your interest in this patch, but I am now working on other projects and currently don't plan to make a version 2 of this patch.
next prev parent reply other threads:[~2022-11-15 4:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 10:09 [RFC PATCH] seccomp: Add protection keys into seccomp_data Stephen Röttger
2022-11-15 4:16 ` Michael Sammler [this message]
2022-11-16 12:20 ` Stephen Röttger
-- strict thread matches above, loose matches on Subject: below --
2018-10-29 11:23 Michael Sammler
2018-10-29 16:25 ` Kees Cook
2018-10-29 16:37 ` Dave Hansen
2018-10-29 16:48 ` Jann Horn
2018-10-29 17:02 ` Michael Sammler
2018-10-29 17:07 ` Dave Hansen
2018-10-29 17:29 ` Dave Hansen
2018-10-29 21:55 ` Michael Sammler
2018-10-29 22:33 ` Dave Hansen
2018-10-30 10:55 ` Michael Sammler
2018-10-29 16:42 ` Jann Horn
2018-10-29 16:48 ` Ram Pai
2018-10-29 17:05 ` Michael Sammler
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=0a643215-03ce-4388-bd1a-301dcab87c41@mpi-sws.org \
--to=msammler@mpi-sws.org \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=luto@amacapital.net \
--cc=sroettger@google.com \
--cc=wad@chromium.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).