summaryrefslogtreecommitdiff
path: root/utility
diff options
context:
space:
mode:
authorHung-Te Lin <hungte@chromium.org>2018-11-01 17:23:55 +0800
committerchrome-bot <chrome-bot@chromium.org>2018-11-19 07:09:16 -0800
commit9071205452595027cc8d52588f0c6fdf7581f905 (patch)
treeac8975f2859994677887eaced0127f59e2357208 /utility
parent4f3bd486afa000910d383fe7b7d6b6b7cc779dbe (diff)
downloadvboot-9071205452595027cc8d52588f0c6fdf7581f905.tar.gz
futility: updater: Need --force when re-keying to DEV keys
For dogfood devices, we usually will only re-key from DEV to PreMP, and then PreMP to MP. It was found that for retail devices, if WP was disabled (unintended), user may accidentally re-key to DEV keys if they (1) recover with a DEV-signed image, or (2) received an AU that didn't have right signing keys. As a result, we want to make it harder when recovering to DEV keys. BUG=chromium:894324 TEST=make futil; tests/futility/run_test_scripts.sh $(pwd)/build/futility BRANCH=None Change-Id: Id3f7788e6c86d12b6e37b77818a1b4c2ceda1e2f Signed-off-by: Hung-Te Lin <hungte@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1312596 Reviewed-by: Mike Frysinger <vapier@chromium.org>
Diffstat (limited to 'utility')
0 files changed, 0 insertions, 0 deletions