diff options
| author | Mimi Zohar <[email protected]> | 2020-01-23 22:24:35 +0000 |
|---|---|---|
| committer | Mimi Zohar <[email protected]> | 2020-01-23 22:24:35 +0000 |
| commit | d54e17b4066612d88c4ef3e5fb3115f12733763d (patch) | |
| tree | 3290001b6ae913d289b6eedb60f59acce50d64bf /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | IMA: pre-allocate buffer to hold keyrings string (diff) | |
| parent | IMA: Defined delayed workqueue to free the queued keys (diff) | |
| download | kernel-d54e17b4066612d88c4ef3e5fb3115f12733763d.tar.gz kernel-d54e17b4066612d88c4ef3e5fb3115f12733763d.zip | |
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/[email protected]/
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions