From: Kees Cook <kees@kernel.org>
To: Casey Schaufler <casey@schaufler-ca.com>,
Kees Cook <keescook@chromium.org>,
Paul Moore <paul@paul-moore.com>
Cc: "James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org,
"Mickaël Salaün" <mic@digikod.net>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-hardening@vger.kernel.org, casey@schaufler-ca.com
Subject: Re: [PATCH v2] LSM: Better reporting of actual LSMs at boot
Date: Tue, 01 Nov 2022 17:52:58 -0700 [thread overview]
Message-ID: <970317F3-D1A2-412D-88EF-18A606AC1E6A@kernel.org> (raw)
In-Reply-To: <a737ec91-0eba-94dc-46dc-683abdc96366@schaufler-ca.com>
On November 1, 2022 5:46:55 PM PDT, Casey Schaufler <casey@schaufler-ca.com> wrote:
>On 11/1/2022 5:05 PM, Kees Cook wrote:
>> Enhance the details reported by "lsm.debug" in several ways:
> [...]
>
>Acked-by: Casey Schaufler <casey@schaufler-ca.com>
Thanks!
>I'm curious about what is driving this change.
I was working on the ima stacking PoC and found the lsm.debug output confusing to read, and I wrote it. :P So, I wanted to clarify things and make sure stuff like lockdown was visible. Additionally, if we're going to keep the "lsm=" param as-is, I wanted it's value visible at boot so people would know what to start from when making changes.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2022-11-02 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 0:05 Kees Cook
2022-11-02 0:46 ` Casey Schaufler
2022-11-02 0:52 ` Kees Cook [this message]
2022-11-03 16:09 ` Mickaël Salaün
2022-11-16 23:04 ` Paul Moore
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=970317F3-D1A2-412D-88EF-18A606AC1E6A@kernel.org \
--to=kees@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--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
all inboxes | Powered by JetHome®