summaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorBill Richardson <wfrichar@chromium.org>2015-10-12 13:58:12 -0700
committerchrome-bot <chrome-bot@chromium.org>2015-10-13 20:22:04 -0700
commit7ed261297f7b730e9f545ba59cbe2ed216850e19 (patch)
tree32de7b1658af2d9ee19158284ffcd2b8f7cd72b7 /Makefile
parent12a55f255aaea2f12362e4f832a0bd48eb29f5dd (diff)
downloadvboot-7ed261297f7b730e9f545ba59cbe2ed216850e19.tar.gz
futility: Support for signing RO+RW firmwarestabilize-smaug-7547.B
This adds the "rwsig" type, with initial support for RO+RW firmware images that need to verify themselves instead of using software sync. This uses our vb2 structs instead of raw binary blobs. That will help us locate, identify, and verify the keys and signatures in the signed firmware images. BUG=chrome-os-partner:46254 BRANCH=smaug,ToT TEST=make runtests I also hacked up a test board with the EC-side signature verification routines from a preliminary CL and tested this signing scheme with that. It works. Additional work is needed to make this seamless, but you can try it out like so: futility create ./tests/testkeys/key_rsa2048.pem foo futility sign --type rwsig --prikey foo.vbprik2 --pubkey foo.vbpubk2 ec.bin Change-Id: I876ab312a2b0b36411c5f739fe3252529728d034 Signed-off-by: Bill Richardson <wfrichar@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/305394 Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile1
1 files changed, 1 insertions, 0 deletions
diff --git a/Makefile b/Makefile
index 225097fc..40d2422c 100644
--- a/Makefile
+++ b/Makefile
@@ -632,6 +632,7 @@ FUTIL_SRCS = \
futility/cmd_vbutil_keyblock.c \
futility/file_type.c \
futility/file_type_bios.c \
+ futility/file_type_rwsig.c \
futility/file_type_usbpd1.c \
futility/vb1_helper.c \
futility/vb2_helper.c