Re: [PATCH 2/2] integrity: double check iint_cache was initialized
From: Casey Schaufler <casey@schaufler-ca.com>
Date: 2022-02-24 17:32:39
Also in:
linux-integrity, lkml
From: Casey Schaufler <casey@schaufler-ca.com>
Date: 2022-02-24 17:32:39
Also in:
linux-integrity, lkml
On 2/24/2022 6:20 AM, Petr Vorel wrote:
Hi Mimi, Tetsuo, Kees, all,
FYI this commit merged as 92063f3ca73a ("integrity: double check iint_cache was initialized")
is the reason for openSUSE distro installer going back from lsm= to deprecated
security= when filling default grub parameters because security=apparmor or
security=selinux does not break boot when used with ima_policy=tcb, unlike
using lsm.OK, color me confused. Integrity isn't an LSM. It doesn't call security_add_hooks().
@Kees, @Mimi sure, people who use ima_policy=tcb will just remove lsm parameter or add "integrity" to it but I wonder whether there could be "integrity" automatic inclusion when using ima_policy=tcb. Although the point of lsm= (and CONFIG_LSM) is to have *ordered* list of enabled LSMs and it wouldn't be clear on which place.
Why would adding integrity to the lsm= make sense? It's not an LSM. Sorry, but something is wrong here.
Kind regards, Petr