diff options
author | Thiago Jung Bauermann <bauerman@linux.ibm.com> | 2019-06-27 23:19:33 -0300 |
---|---|---|
committer | Mimi Zohar <zohar@linux.ibm.com> | 2019-08-05 18:40:26 -0400 |
commit | e5092255bb3967bcc473dc86492dbbd5f7714023 (patch) | |
tree | 69dab56bf638a2404728c24a486eb8444f58a9a8 /net/ipv4/ipmr_base.c | |
parent | 3878d505aa718bcc7b1eb4089ab9b9fb27dee957 (diff) | |
download | linux-stable-e5092255bb3967bcc473dc86492dbbd5f7714023.tar.gz linux-stable-e5092255bb3967bcc473dc86492dbbd5f7714023.tar.bz2 linux-stable-e5092255bb3967bcc473dc86492dbbd5f7714023.zip |
ima: Store the measurement again when appraising a modsig
If the IMA template contains the "modsig" or "d-modsig" field, then the
modsig should be added to the measurement list when the file is appraised.
And that is what normally happens, but if a measurement rule caused a file
containing a modsig to be measured before a different rule causes it to be
appraised, the resulting measurement entry will not contain the modsig
because it is only fetched during appraisal. When the appraisal rule
triggers, it won't store a new measurement containing the modsig because
the file was already measured.
We need to detect that situation and store an additional measurement with
the modsig. This is done by adding an IMA_MEASURE action flag if we read a
modsig and the IMA template contains a modsig field.
Suggested-by: Mimi Zohar <zohar@linux.ibm.com>
Signed-off-by: Thiago Jung Bauermann <bauerman@linux.ibm.com>
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
Diffstat (limited to 'net/ipv4/ipmr_base.c')
0 files changed, 0 insertions, 0 deletions