From: bauen1 <j2468h@googlemail.com>
To: mic@digikod.net
Cc: akpm@linux-foundation.org, arnd@arndb.de, casey@schaufler-ca.com,
christian.brauner@ubuntu.com, christian@python.org,
corbet@lwn.net, cyphar@cyphar.com,
deven.desai@linux.microsoft.com, dvyukov@google.com,
ebiggers@kernel.org, ericchiang@google.com, fweimer@redhat.com,
geert@linux-m68k.org, jack@suse.cz, jannh@google.com,
jmorris@namei.org, keescook@chromium.org,
kernel-hardening@lists.openwall.com, linux-api@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, luto@kernel.org,
madvenka@linux.microsoft.com, mjg59@google.com,
mszeredi@redhat.com, mtk.manpages@gmail.com,
nramas@linux.microsoft.com, philippe.trebuchet@ssi.gouv.fr,
scottsh@microsoft.com, sean.j.christopherson@intel.com,
sgrubb@redhat.com, shuah@kernel.org, steve.dower@python.org,
thibaut.sautereau@clip-os.org, vincent.strubel@ssi.gouv.fr,
viro@zeniv.linux.org.uk, willy@infradead.org,
zohar@linux.ibm.com
Subject: Re: [PATCH v12 0/3] Add trusted_for(2) (was O_MAYEXEC)
Date: Fri, 9 Apr 2021 18:26:49 +0200 [thread overview]
Message-ID: <d3b0da18-d0f6-3f72-d3ab-6cf19acae6eb@gmail.com> (raw)
In-Reply-To: <20201203173118.379271-1-mic@digikod.net>
Hello,
As a user of SELinux I'm quite interested in the trusted_for / O_MAYEXEC changes in the kernel and userspace.
However the last activity on this patch seems to be this email from 2020-12-03 with no replies, so what is the status of this patchset or is there something that I'm missing ?
https://patchwork.kernel.org/project/linux-security-module/list/?series=395617
https://lore.kernel.org/linux-security-module/20201203173118.379271-1-mic@digikod.net/
next prev parent reply other threads:[~2021-04-09 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 17:31 [PATCH v12 0/3] Add trusted_for(2) (was O_MAYEXEC) Mickaël Salaün
2020-12-03 17:31 ` [PATCH v12 1/3] fs: Add trusted_for(2) syscall implementation and related sysctl Mickaël Salaün
2020-12-03 17:31 ` [PATCH v12 2/3] arch: Wire up trusted_for(2) Mickaël Salaün
2020-12-03 17:31 ` [PATCH v12 3/3] selftest/interpreter: Add tests for trusted_for(2) policies Mickaël Salaün
2021-04-09 16:26 ` bauen1 [this message]
2021-04-09 17:15 ` [PATCH v12 0/3] Add trusted_for(2) (was O_MAYEXEC) Mickaël Salaün
2021-10-06 22:03 ` Kees Cook
2021-10-07 18:29 ` Mickaël Salaün
2021-10-07 18:37 ` Mimi Zohar
2021-10-07 19:00 ` Mickaël Salaün
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=d3b0da18-d0f6-3f72-d3ab-6cf19acae6eb@gmail.com \
--to=j2468h@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=casey@schaufler-ca.com \
--cc=christian.brauner@ubuntu.com \
--cc=christian@python.org \
--cc=corbet@lwn.net \
--cc=cyphar@cyphar.com \
--cc=deven.desai@linux.microsoft.com \
--cc=dvyukov@google.com \
--cc=ebiggers@kernel.org \
--cc=ericchiang@google.com \
--cc=fweimer@redhat.com \
--cc=geert@linux-m68k.org \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@kernel.org \
--cc=madvenka@linux.microsoft.com \
--cc=mic@digikod.net \
--cc=mjg59@google.com \
--cc=mszeredi@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=nramas@linux.microsoft.com \
--cc=philippe.trebuchet@ssi.gouv.fr \
--cc=scottsh@microsoft.com \
--cc=sean.j.christopherson@intel.com \
--cc=sgrubb@redhat.com \
--cc=shuah@kernel.org \
--cc=steve.dower@python.org \
--cc=thibaut.sautereau@clip-os.org \
--cc=vincent.strubel@ssi.gouv.fr \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=zohar@linux.ibm.com \
/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).