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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Oct 2022 15:37:57 -0700 From: Kees Cook <keescook@...omium.org> To: Mimi Zohar <zohar@...ux.ibm.com> Cc: Mickaël Salaün <mic@...ikod.net>, Paul Moore <paul@...l-moore.com>, James Morris <jmorris@...ei.org>, "Serge E. Hallyn" <serge@...lyn.com>, Dmitry Kasatkin <dmitry.kasatkin@...il.com>, linux-security-module@...r.kernel.org, linux-integrity@...r.kernel.org, KP Singh <kpsingh@...nel.org>, Casey Schaufler <casey@...aufler-ca.com>, John Johansen <john.johansen@...onical.com>, linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org Subject: Re: [PATCH 1/9] integrity: Prepare for having "ima" and "evm" available in "integrity" LSM On Wed, Oct 19, 2022 at 03:13:34PM -0400, Mimi Zohar wrote: > Most people were/are still using the "security=" boot command line > option, not "lsm=". This previously wasn't a problem with "security=", > but became a problem with "lsm=". How are people still using "security=" for IMA/EVM? It only interacts with LSMs marked with LSM_FLAG_LEGACY_MAJOR. -- Kees Cook
Powered by blists - more mailing lists