-
Notifications
You must be signed in to change notification settings - Fork 364
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FAPI: Add event logging for firmware and IMA events.
Add serialization and deserialization for firmware events: * Serialization and deserialization of firmware events specified in the TCG PC Client Platform Firmware Profile was added. * Also for the firmare legacy format (sha1) the serialization and deserialization was added. Add serialization and deserialization for IMA events: * Serialization of IMA events as described on: https://sourceforge.net/p/linux-ima/wiki/Home/ was added. The templates ima, img-sig, ima-ng, and ima-sig are supported. * Tests in fapi-jons.c were adapted. Integrate firmware and IMA eventlog: * Since fapi logging of IMA and firmware events is only a preview version this functionality has to be explicitly activated with a configure switch. * The IMA event logging was integrated. * The PC-Client firmware logging was integrated. CEL Events: * The cel_version event was added as first event for the event log of PCR 0. * The firmware_end event was added behind the last firmware event. * Serialization and deserialization of CEL events was added. Event logging: * For invalid digests an error will only produced for quote verification. In other cases only a warning will be displayed. * rename "type" to "content_type". * rename "sub_event" to "content". Tests for event logging for firmware and IMA events: * An Unit test for several binary examples was added. * Tests in fapi-jons.c were adapted. * Copied functions were removed from unit test fapi-json.c * An Integration test for The PC-Client firmware logging was added. * An Integration test for The PC-Client firmware logging in the legacy format was added. Signed-off-by: Juergen Repp <juergen.repp@sit.fraunhofer.de>
- Loading branch information
1 parent
57869f5
commit 7cb07d8
Showing
56 changed files
with
6,056 additions
and
299 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.