summaryrefslogtreecommitdiff
path: root/identity/support/src/cppbor_parse.cpp
diff options
context:
space:
mode:
authorMatthew Maurer <mmaurer@google.com>2019-05-10 13:52:03 -0700
committerJay Patel <pateljay@google.com>2020-01-06 23:54:57 +0000
commit9f35c5223b3076d6ae30799f80946307ba60e33f (patch)
tree7242f83fd57f17468de22e893b108b7706a1394b /identity/support/src/cppbor_parse.cpp
parent13c9e764eb58f9d802270b05c7f18e6743261702 (diff)
Use SHA_2_256 for importWrappedKey
The spec requires that SHA1 not be allowed for wrapped keys and that only SHA_2_256 be used. Unfortunately, the previous VTS required SHA1 support. This patch takes the middle ground by requiring SHA_2_256 be supported for importWrappedKey, but not disallowing it from supporting SHA1. This makes it possible for a spec compliant keymaster to pass VTS while not disqualifying shipped devices. Bug: 140789517 Bug: 129291873 Test: atest VtsHalKeymasterV4_0TargetTest:ImportWrappedKeyTest, Trusty Change-Id: I6c3a9182b51f2e7a46173d5bfc34d3c3264d954f (cherry picked from commit 41cb84029ae02e5836d20a12de7778d70ea3a3da)
Diffstat (limited to 'identity/support/src/cppbor_parse.cpp')
0 files changed, 0 insertions, 0 deletions