summaryrefslogtreecommitdiffstats
path: root/arch/sparc
diff options
context:
space:
mode:
authorMimi Zohar <zohar@linux.vnet.ibm.com>2016-09-29 10:04:52 -0400
committerMimi Zohar <zohar@linux.vnet.ibm.com>2017-12-18 09:43:38 -0500
commitda1b0029f527a9b4204e90ba6f14ee139fd76f9e (patch)
treeaf35d10ffe5d0fec77a5515a78c0098861fc9cf8 /arch/sparc
parent0d73a55208e94fc9fb6deaeea61438cd3280d4c0 (diff)
downloadop-kernel-dev-da1b0029f527a9b4204e90ba6f14ee139fd76f9e.zip
op-kernel-dev-da1b0029f527a9b4204e90ba6f14ee139fd76f9e.tar.gz
ima: support new "hash" and "dont_hash" policy actions
The builtin ima_appraise_tcb policy, which is specified on the boot command line, can be replaced with a custom policy, normally early in the boot process. Custom policies can be more restrictive in some ways, like requiring file signatures, but can be less restrictive in other ways, like not appraising mutable files. With a less restrictive policy in place, files in the builtin policy might not be hashed and labeled with a security.ima hash. On reboot, files which should be labeled in the ima_appraise_tcb are not labeled, possibly preventing the system from booting properly. To resolve this problem, this patch extends the existing IMA policy actions "measure", "dont_measure", "appraise", "dont_appraise", and "audit" with "hash" and "dont_hash". The new "hash" action will write the file hash as security.ima, but without requiring the file to be appraised as well. For example, the builtin ima_appraise_tcb policy includes the rule, "appraise fowner=0". Adding the "hash fowner=0" rule to a custom policy, will cause the needed file hashes to be calculated and written as security.ima xattrs. Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
Diffstat (limited to 'arch/sparc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud