From: Casey Schaufler <casey@schaufler-ca.com>
To: Kees Cook <keescook@chromium.org>, James Morris <jmorris@namei.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] LSM: Ignore "security=" when "lsm=" is specified
Date: Wed, 13 Feb 2019 08:05:45 -0800 [thread overview]
Message-ID: <5260689d-9016-bdf4-6070-13d2c88ac8a8@schaufler-ca.com> (raw)
In-Reply-To: <20190212182318.GA16669@beast>
On 2/12/2019 10:23 AM, Kees Cook wrote:
> To avoid potential confusion, explicitly ignore "security=" when "lsm=" is
> used on the command line, and report that it is happening.
>
> Suggested-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Acked-by: Casey Schaufler <casey@schaufler-ca.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 10 ++++------
> security/security.c | 8 ++++++--
> 2 files changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 93d2c97f28fe..a0abd5f56e00 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -2340,7 +2340,7 @@
>
> lsm=lsm1,...,lsmN
> [SECURITY] Choose order of LSM initialization. This
> - overrides CONFIG_LSM.
> + overrides CONFIG_LSM, and the "security=" parameter.
>
> machvec= [IA-64] Force the use of a particular machine-vector
> (machvec) in a generic kernel.
> @@ -4129,11 +4129,9 @@
> Note: increases power consumption, thus should only be
> enabled if running jitter sensitive (HPC/RT) workloads.
>
> - security= [SECURITY] Choose a security module to enable at boot.
> - If this boot parameter is not specified, only the first
> - security module asking for security registration will be
> - loaded. An invalid security module name will be treated
> - as if no module has been chosen.
> + security= [SECURITY] Choose a legacy "major" security module to
> + enable at boot. This has been deprecated by the
> + "lsm=" parameter.
>
> selinux= [SELINUX] Disable or enable SELinux at boot time.
> Format: { "0" | "1" }
> diff --git a/security/security.c b/security/security.c
> index 3147785e20d7..23cbb1a295a3 100644
> --- a/security/security.c
> +++ b/security/security.c
> @@ -288,9 +288,13 @@ static void __init ordered_lsm_init(void)
> ordered_lsms = kcalloc(LSM_COUNT + 1, sizeof(*ordered_lsms),
> GFP_KERNEL);
>
> - if (chosen_lsm_order)
> + if (chosen_lsm_order) {
> + if (chosen_major_lsm) {
> + pr_info("security= is ignored because it is superseded by lsm=\n");
> + chosen_major_lsm = NULL;
> + }
> ordered_lsm_parse(chosen_lsm_order, "cmdline");
> - else
> + } else
> ordered_lsm_parse(builtin_lsm_order, "builtin");
>
> for (lsm = ordered_lsms; *lsm; lsm++)
next prev parent reply other threads:[~2019-02-13 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:23 Kees Cook
2019-02-13 16:05 ` Casey Schaufler [this message]
2019-02-17 5:16 ` Tetsuo Handa
2019-02-18 2:45 ` Paul Moore
2019-02-18 3:57 ` Kees Cook
2019-02-25 23:23 ` James Morris
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=5260689d-9016-bdf4-6070-13d2c88ac8a8@schaufler-ca.com \
--to=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=penguin-kernel@i-love.sakura.ne.jp \
/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
all inboxes | Powered by JetHome®