summaryrefslogtreecommitdiff
path: root/host
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2019-01-15 18:07:23 +0800
committerChromeOS Commit Bot <chromeos-commit-bot@chromium.org>2019-01-22 16:53:37 +0000
commitfbea9a78e11d2a2c9171dad3f630884badfe3e43 (patch)
treef5b487970f4a5b68d4f36b6836fd6120f685e67b /host
parent8cc7413dc80a675b40f54f74407d2ae4bce9a1a3 (diff)
downloadvboot-stabilize-11316.146.B.tar.gz
Starting from GBB 1.2, a digest is stored in GBB and must be updated whenever the HWID string is changed. In shell script version of updater, the digest is automatically updated when we do "futility gbb -s --hwid=XXX", but in native updater implementation we only updated the HWID string and left digest unchanged, this leaves devices generating wrong PCR1 values. `cmd_gbb_utility` updates the digest by calling `update_hwid_digest` using vboot1 structure, so we should introduce a new vboot2 friendly function, `vb2_change_hwid`, which changes both HWID string and digest at same time. Note this has no impact for end user's devices with write protection enabled. Only changes dogfood units AU results. BUG=b:122248649 TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility BRANCH=none Change-Id: I6ad2754e6df3c9dd66d71c560a2afc26d14eae33 Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1411932 Reviewed-by: Joel Kitching <kitching@chromium.org> (cherry picked from commit 859682accb19893803026a28b4c8ca2cd57945a4) Reviewed-on: https://chromium-review.googlesource.com/c/1423940 Tested-by: James Chen <chienhua@google.com> Trybot-Ready: James Chen <chienhua@google.com> Reviewed-by: John Chen <zuan@chromium.org> Reviewed-by: Srinivasa duvvuri <sduvvuri@google.com> Commit-Queue: John Chen <zuan@chromium.org>
Diffstat (limited to 'host')
0 files changed, 0 insertions, 0 deletions