From: "Mickaël Salaün" <mic@digikod.net>
To: James Morris <jmorris@namei.org>, "Serge E . Hallyn" <serge@hallyn.com>
Cc: "Mickaël Salaün" <mic@digikod.net>,
"Casey Schaufler" <casey@schaufler-ca.com>,
"Kees Cook" <keescook@chromium.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [PATCH v3 0/1] Automatic LSM stack ordering
Date: Mon, 22 Feb 2021 16:06:07 +0100 [thread overview]
Message-ID: <20210222150608.808146-1-mic@digikod.net> (raw)
Hi,
This patch series gives the opportunity to users to not manually
configure the list of LSM enabled at boot but instead always rely on the
up-to-date list of existing LSMs. Indeed, CONFIG_LSM may never be
updated with a make oldconfig whereas users may select new LSMs over
time. With this patch, when running make oldconfig, a new option
CONFIG_LSM_AUTO is pre-selected to delegate LSM ordering to the kernel
developers, according to the user configuration.
This third series replace the previous virtual dependencies with a new
option to automatically enable all selected LSMs. This is cleaner,
simpler, and makes the transition more convenient.
This patch series can be applied on v5.11-7580-gea914b7ffbfd (or v5.11).
Previous version:
https://lore.kernel.org/r/20210215181511.2840674-1-mic@digikod.net
Mickaël Salaün (1):
security: Add CONFIG_LSM_AUTO to handle default LSM stack ordering
security/Kconfig | 19 +++++++++++++++++++
security/security.c | 26 +++++++++++++++++++++++++-
2 files changed, 44 insertions(+), 1 deletion(-)
base-commit: 31caf8b2a847214be856f843e251fc2ed2cd1075
--
2.30.0
next reply other threads:[~2021-02-22 15:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 15:06 Mickaël Salaün [this message]
2021-02-22 15:06 ` [PATCH v3 1/1] security: Add CONFIG_LSM_AUTO to handle default LSM stack ordering Mickaël Salaün
2021-02-22 16:51 ` Casey Schaufler
2021-02-22 18:31 ` Mickaël Salaün
2021-02-22 20:31 ` Casey Schaufler
2021-02-22 21:12 ` Nicolas Iooss
2021-02-22 22:46 ` Casey Schaufler
2021-02-23 6:21 ` Nicolas Iooss
2022-10-17 19:25 ` Kees Cook
2022-10-18 1:45 ` Paul Moore
2022-10-18 5:55 ` Kees Cook
2022-10-18 19:31 ` Paul Moore
2022-11-04 16:29 ` Mickaël Salaün
2022-11-04 17:20 ` Casey Schaufler
2022-11-07 12:35 ` Mickaël Salaün
2022-11-07 17:21 ` Casey Schaufler
2022-11-07 19:37 ` Mickaël Salaün
2022-10-20 16:00 ` Casey Schaufler
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=20210222150608.808146-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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).