diff options
| author | Julius Werner <jwerner@chromium.org> | 2019-07-17 14:44:16 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-07-25 20:38:36 -0700 |
| commit | 0e2e748940b7a48b8b056700dc0d081928c63c2e (patch) | |
| tree | f54593e27c5a263f4818373cf15f7b4aef3164b1 /cgpt/cmd_boot.c | |
| parent | e050a2c88fc963cb97d9794849e9e2b60fabbe77 (diff) | |
| download | vboot-stabilize-12371.39.B.tar.gz | |
sign_official_build.sh: Update kern_b_hash to support SHA256stabilize-octopus-12371.15.Bstabilize-12386.Bstabilize-12371.89.Bstabilize-12371.82.Bstabilize-12371.81.Bstabilize-12371.80.Bstabilize-12371.75.Bstabilize-12371.71.Bstabilize-12371.65.Bstabilize-12371.52.Bstabilize-12371.50.Bstabilize-12371.39.Bstabilize-12371.27.Bstabilize-12371.26.Bstabilize-12371.11.Brelease-R77-12371.B
We're updating the algorithm for this so the signing scripts have to
support it as well. Since we're running ToT signing scripts on older
images as well, determine the hash algorithm used in the image by
checking its length (40 hex digits for SHA1, 64 for SHA256).
BRANCH=None
BUG=b:137576540
TEST=$(sign_official_build.sh recovery recovery_image.bin
/tmp/scratch/mykeys/ resigned_image.bin) -- used futility to confirm
that new image kern_b_hash matches new image KERN-B and uses the
expected algorithm (tried with both SHA1 and SHA256)
Cq-Depend: chromium:1706624
Change-Id: Ie1a62ad1fd4fbf141cc1c32d592b863f2d43a24e
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1707529
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Diffstat (limited to 'cgpt/cmd_boot.c')
0 files changed, 0 insertions, 0 deletions