diff options
author | Roberto Sassu <roberto.sassu@huawei.com> | 2020-03-25 11:47:06 +0100 |
---|---|---|
committer | Mimi Zohar <zohar@linux.ibm.com> | 2020-04-19 22:03:39 -0400 |
commit | 6f1a1d103b48b1533a9c804e7a069e2c8e937ce7 (patch) | |
tree | f081c5a832103b1d491060e480cdc4bf205919d0 /security/integrity/ima/ima_main.c | |
parent | ae83d0b416db002fe95601e7f97f64b59514d936 (diff) | |
download | lwn-6f1a1d103b48b1533a9c804e7a069e2c8e937ce7.tar.gz lwn-6f1a1d103b48b1533a9c804e7a069e2c8e937ce7.zip |
ima: Switch to ima_hash_algo for boot aggregate
boot_aggregate is the first entry of IMA measurement list. Its purpose is
to link pre-boot measurements to IMA measurements. As IMA was designed to
work with a TPM 1.2, the SHA1 PCR bank was always selected even if a
TPM 2.0 with support for stronger hash algorithms is available.
This patch first tries to find a PCR bank with the IMA default hash
algorithm. If it does not find it, it selects the SHA256 PCR bank for
TPM 2.0 and SHA1 for TPM 1.2. Ultimately, it selects SHA1 also for TPM 2.0
if the SHA256 PCR bank is not found.
If none of the PCR banks above can be found, boot_aggregate file digest is
filled with zeros, as for TPM bypass, making it impossible to perform a
remote attestation of the system.
Cc: stable@vger.kernel.org # 5.1.x
Fixes: 879b589210a9 ("tpm: retrieve digest size of unknown algorithms with PCR read")
Reported-by: Jerry Snitselaar <jsnitsel@redhat.com>
Suggested-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'security/integrity/ima/ima_main.c')
0 files changed, 0 insertions, 0 deletions