Use VbSharedData instead of VbNvStorage for fwb_tries and kernkey_vfy

Change-Id: I5ed3509a9d4e578cd2e98f493dab59bc2fbd5827

R=dlaurie@chromium.org
BUG=chrome-os-partner:2748
TEST=manual

crossystem fwb_tries=3
(reboot)
crossystem tried_fwb
(should print 1)

crossystem fwb_tries=0
(reboot)
crossystem tried_fwb
(should print 0)

In dev mode...
Boot a kernel signed with the same key as in the firmware
crossystem kernkey_vfy
(should print sig)
Boot a kernel signed with a different key than the firmware
crossystem kernkey_vfy
(should print hash)

Review URL: http://codereview.chromium.org/6711045
This commit is contained in:
Randall Spangler
2011-03-18 12:44:27 -07:00
parent 17c712672f
commit cabe6b3514
6 changed files with 16 additions and 45 deletions

View File

@@ -47,13 +47,6 @@ typedef enum VbNvParam {
VBNV_LOCALIZATION_INDEX,
/* Field reserved for kernel/user-mode use; 32-bit value. */
VBNV_KERNEL_FIELD,
/* Firmware checked RW slot B before slot A on the current boot because
* VBNV_TRY_B_COUNT was non-zero at that time. 0=no; 1=yes. */
VBNV_TRIED_FIRMWARE_B,
/* Firmware verified the kernel key block signature using the key stored
* in the firmware. 0=no, just used the key block hash; 1=yes, used the
* key block signature. */
VBNV_FW_VERIFIED_KERNEL_KEY,
/* Verified boot API function which should generate a test error, if
* error number (below) is non-zero. */
VBNV_TEST_ERROR_FUNC,