GNUBoot
/
coreboot-kgpe-d16
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

security/tpm: Fix references to tpm_setup function 

Change-Id: Ia97ddcd5471f8e5db50f57b67a766f08a08180b1
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Reviewed-on: https://review.coreboot.org/29349
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
This commit is contained in:
Jonathan Neuschäfer 2018-10-29 22:52:42 +01:00 committed by Philipp Deppenwiese
parent dfbe6bd5c3
commit 61322d7ad2
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/security/tpm/tspi/tspi.c
View File

@ -103,10 +103,10 @@ static uint32_t tpm_setup_epilogue(uint32_t result)
/* /*
* tpm_setup starts the TPM and establishes the root of trust for the * tpm_setup starts the TPM and establishes the root of trust for the
* anti-rollback mechanism. SetupTPM can fail for three reasons. 1 A bug. 2 a * anti-rollback mechanism. tpm_setup can fail for three reasons. 1 A bug.
* TPM hardware failure. 3 An unexpected TPM state due to some attack. In * 2 a TPM hardware failure. 3 An unexpected TPM state due to some attack. In
* general we cannot easily distinguish the kind of failure, so our strategy is * general we cannot easily distinguish the kind of failure, so our strategy is
* to reboot in recovery mode in all cases. The recovery mode calls SetupTPM * to reboot in recovery mode in all cases. The recovery mode calls tpm_setup
* again, which executes (almost) the same sequence of operations. There is a * again, which executes (almost) the same sequence of operations. There is a
* good chance that, if recovery mode was entered because of a TPM failure, the * good chance that, if recovery mode was entered because of a TPM failure, the
* failure will repeat itself. (In general this is impossible to guarantee * failure will repeat itself. (In general this is impossible to guarantee