On Thu, 2022-10-13 at 15:36 -0700, Kees Cook wrote: > This moves the trivial hard-coded stacking of IMA LSM hooks into the > existing LSM infrastructure. The only thing trivial about making IMA and EVM LSMs is moving them to LSM hooks. Although static files may be signed and the signatures distributed with the file data through the normal distribution mechanisms (e.g. RPM), other files cannot be signed remotely (e.g. configuration files). For these files, both IMA and EVM may be configured to maintain persistent file state stored as security xattrs in the form of security.ima file hashes or security.evm HMACs. The LSM flexibility of enabling/disabling IMA or EVM on a per boot basis breaks this usage, potentially preventing subsequent boots. -- thanks, Mimi
