summaryrefslogtreecommitdiff
path: root/board/cr50/rma_key_blob.x25519.prod
diff options
context:
space:
mode:
authorVadim Bendebury <vbendeb@chromium.org>2018-05-30 11:56:18 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-06-07 23:33:42 -0700
commit71cb7bd6d866114e4c811f049ccb6869e6b39f64 (patch)
treeaf16ed0e565c2c35f2f587d69e1a8cfec5b28676 /board/cr50/rma_key_blob.x25519.prod
parenta730fd6219d53469a8ca0e74a6631912a24877a3 (diff)
downloadchrome-ec-71cb7bd6d866114e4c811f049ccb6869e6b39f64.tar.gz
cr50: prepare for supporting both x25519 and p256 test keys
The signer script is checking the elf files for presence of test RMA keys, currently hardcoded to be x25519 keys. The algorithm (x25519 vs p256) is going to become a compile time option, the script should be prepared to determine the type of the key at run time, because the script could be used for signing images from different branches, compiled with different config options. The prod p256 key does not yet exist. BRANCH=none BUG=b:73296606 TEST=verified that prod signing images including x25519 keys is still working as expected. Change-Id: Icf48845279912ecc9ccdecec1764fcb5f85d22bd Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1079698 Reviewed-by: Randall Spangler <rspangler@chromium.org> Reviewed-by: Mary Ruthven <mruthven@chromium.org>
Diffstat (limited to 'board/cr50/rma_key_blob.x25519.prod')
-rw-r--r--board/cr50/rma_key_blob.x25519.prodbin0 -> 33 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/board/cr50/rma_key_blob.x25519.prod b/board/cr50/rma_key_blob.x25519.prod
new file mode 100644
index 0000000000..54e8fd5a1d
--- /dev/null
+++ b/board/cr50/rma_key_blob.x25519.prod
Binary files differ