summaryrefslogtreecommitdiff
path: root/src/network/networkd-conf.c
diff options
context:
space:
mode:
authorLans Zhang <lans.zhang2008@gmail.com>2016-10-10 06:59:54 +0800
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2016-10-09 18:59:54 -0400
commit59991e3fe3a71d6b6c743d4a38a2acd887ee7590 (patch)
treefe6dd0846b74b980530143f0d5ad2c6051459c36 /src/network/networkd-conf.c
parent084f5805572c2c4797b87e402c31d82fc9c0623d (diff)
sd-boot: trigger to record further logs to tcg 2.0 final event log area (#4302)
According to TCG EFI Protocol Specification for TPM 2.0 family, all events generated after the invocation of EFI_TCG2_GET_EVENT_LOG shall be stored in an instance of an EFI_CONFIGURATION_TABLE aka EFI TCG 2.0 final events table. Hence, it is necessary to trigger the internal switch through calling get_event_log() in order to allow to retrieve the logs from OS runtime. msekletar: > I've looked at EDK2 and indeed log entry is added to FinalEventsTable only after > EFI_TCG2_PROTOCOL.GetEventLog was called[1][2]. Also, same patch was currently > merged to shim by Peter Jones [3]. [1] https://github.com/tianocore/edk2/blob/master/SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c#L698 [2] https://github.com/tianocore/edk2/blob/master/SecurityPkg/Tcg/Tcg2Dxe/Tcg2Dxe.c#L824 [3] rhinstaller/shim#64
Diffstat (limited to 'src/network/networkd-conf.c')
0 files changed, 0 insertions, 0 deletions