linux-hardening - Re: [PATCH v2] LSM: Better reporting of actual LSMs at boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 01 Nov 2022 17:52:58 -0700
From:   Kees Cook <kees@...nel.org>
To:     Casey Schaufler <casey@...aufler-ca.com>,
        Kees Cook <keescook@...omium.org>,
        Paul Moore <paul@...l-moore.com>
CC:     James Morris <jmorris@...ei.org>,
        "Serge E. Hallyn" <serge@...lyn.com>,
        linux-security-module@...r.kernel.org,
        Mickaël Salaün <mic@...ikod.net>,
        linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
        linux-hardening@...r.kernel.org, casey@...aufler-ca.com
Subject: Re: [PATCH v2] LSM: Better reporting of actual LSMs at boot

On November 1, 2022 5:46:55 PM PDT, Casey Schaufler <casey@...aufler-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@...aufler-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