summaryrefslogtreecommitdiff
path: root/firmware/2lib/include/2return_codes.h
diff options
context:
space:
mode:
authorChromeOS Developer <rspangler@chromium.org>2014-12-03 12:19:22 -0800
committerchrome-internal-fetch <chrome-internal-fetch@google.com>2014-12-04 04:02:05 +0000
commit7aef90c14d9dc770b4e16876faf8bf6b9942ff2e (patch)
tree0d6904fb26f9fde95d2fc614ad9864c2a7f159d1 /firmware/2lib/include/2return_codes.h
parenta5b69b02e039d7267390fea10266d45e14630559 (diff)
downloadvboot-7aef90c14d9dc770b4e16876faf8bf6b9942ff2e.tar.gz
vboot2: vb2_unpack_key2() no longer passes through to vb2_unpack_key()
At one point I thought I'd be able to support both vboot1 and vboot2.1 data structures and dynamically determine which verification path to run. But space limitations on current platforms (e.g. pinky) mean that's not feasible. Remove this vestigal support, so that it's easier to make a clean break to the new data structures on appropriate platforms. BUG=chromium:423882 BRANCH=none TEST=make runtests && VBOOT2=1 make runtests (works with/withoug VBOOT2 flag) And build firmware for veyron_pinky. Change-Id: I9887e0c54114c475df81d5a2b701b9b52e95b017 Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/232979 Reviewed-by: Bill Richardson <wfrichar@chromium.org>
Diffstat (limited to 'firmware/2lib/include/2return_codes.h')
-rw-r--r--firmware/2lib/include/2return_codes.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/firmware/2lib/include/2return_codes.h b/firmware/2lib/include/2return_codes.h
index 3d1c611a..f41d784e 100644
--- a/firmware/2lib/include/2return_codes.h
+++ b/firmware/2lib/include/2return_codes.h
@@ -226,6 +226,9 @@ enum vb2_return_code {
/* Key algorithm doesn't match signature algorithm */
VB2_ERROR_VDATA_ALGORITHM_MISMATCH,
+ /* Bad magic number in vb2_unpack_key2() */
+ VB2_ERROR_UNPACK_KEY_MAGIC,
+
/**********************************************************************
* Keyblock verification errors (all in vb2_verify_keyblock())
*/