diff options
| author | Vadim Bendebury <vbendeb@chromium.org> | 2017-09-28 12:57:33 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2017-10-02 23:28:23 -0700 |
| commit | 34ce0a90a59979f7a82e7efdd41481370fb31498 (patch) | |
| tree | 8d2045526bd9da0a0eb9de849bac12c4e19c5c95 /power | |
| parent | 5ee37253d7213964c8a19129932fc68d30f10aae (diff) | |
| download | chrome-ec-34ce0a90a59979f7a82e7efdd41481370fb31498.tar.gz | |
commom: generalize rma_auth to and make it match server expectations
Different devices could have different sized unique device IDs. Let's
just use the IDs as is if they are no larger than the
rma_challenge:device_id field, or the first 8 bytes of the HMAC_sha256
value of the unique device ID, where the unique device ID is used both
as the key and the payload.
The server expects the board ID field in big endian format, let's swap
it before calculating the RMA auth challenge.
The test's server side implementation needs to be also adjusted.
BRANCH=cr50
BUG=b:37952913
TEST=make buildall -j passes. With the rest of the patches applied RMA
authentication process generates sensible values.
Change-Id: Ia1fbf9161e01de30a2da8214258008f6e5f7d915
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/690991
Reviewed-by: Michael Tang <ntang@chromium.org>
Diffstat (limited to 'power')
0 files changed, 0 insertions, 0 deletions