From: Mimi Zohar Date: Thu, 23 Jan 2020 22:24:35 +0000 (-0500) Subject: Merge branch 'next-integrity.defer-measuring-keys' into next-integrity X-Git-Tag: v5.6-rc1~144^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d54e17b4066612d88c4ef3e5fb3115f12733763d;p=thirdparty%2Flinux.git Merge branch 'next-integrity.defer-measuring-keys' into next-integrity From patch set cover letter: The IMA subsystem supports measuring asymmetric keys when the key is created or updated[1]. But keys created or updated before a custom IMA policy is loaded are currently not measured. This includes keys added, for instance, to either the .ima or .builtin_trusted_keys keyrings, which happens early in the boot process. Measuring the early boot keys, by design, requires loading a custom IMA policy. This change adds support for queuing keys created or updated before a custom IMA policy is loaded. The queued keys are processed when a custom policy is loaded. Keys created or updated after a custom policy is loaded are measured immediately (not queued). In the case when a custom policy is not loaded within 5 minutes of IMA initialization, the queued keys are freed. [1] https://lore.kernel.org/linux-integrity/20191211164707.4698-1-nramas@linux.microsoft.com/ --- d54e17b4066612d88c4ef3e5fb3115f12733763d