diff options
author | Roberto Sassu <roberto.sassu@polito.it> | 2014-02-03 13:56:04 +0100 |
---|---|---|
committer | Mimi Zohar <zohar@linux.vnet.ibm.com> | 2014-03-07 11:32:29 -0500 |
commit | c019e307ad82a8ee652b8ccbacf69ae94263b07b (patch) | |
tree | 8c212430952cec1db5611d51718a78fbcbad7674 /tools/thermal | |
parent | 73a6b44a003ad5dd1af9a8d05f01589dce7cd47a (diff) | |
download | linux-c019e307ad82a8ee652b8ccbacf69ae94263b07b.tar.gz linux-c019e307ad82a8ee652b8ccbacf69ae94263b07b.tar.bz2 linux-c019e307ad82a8ee652b8ccbacf69ae94263b07b.zip |
ima: restore the original behavior for sending data with ima template
With the new template mechanism introduced in IMA since kernel 3.13,
the format of data sent through the binary_runtime_measurements interface
is slightly changed. Now, for a generic measurement, the format of
template data (after the template name) is:
template_len | field1_len | field1 | ... | fieldN_len | fieldN
In addition, fields containing a string now include the '\0' termination
character.
Instead, the format for the 'ima' template should be:
SHA1 digest | event name length | event name
It must be noted that while in the IMA 3.13 code 'event name length' is
'IMA_EVENT_NAME_LEN_MAX + 1' (256 bytes), so that the template digest
is calculated correctly, and 'event name' contains '\0', in the pre 3.13
code 'event name length' is exactly the string length and 'event name'
does not contain the termination character.
The patch restores the behavior of the IMA code pre 3.13 for the 'ima'
template so that legacy userspace tools obtain a consistent behavior
when receiving data from the binary_runtime_measurements interface
regardless of which kernel version is used.
Signed-off-by: Roberto Sassu <roberto.sassu@polito.it>
Cc: <stable@vger.kernel.org> # 3.3.13: 3ce1217 ima: define template fields library
Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
Diffstat (limited to 'tools/thermal')
0 files changed, 0 insertions, 0 deletions