Merge "Match usage entry to header" into rvc-dev
This commit is contained in:
committed by
Android (Google) Code Review
commit
042efc971d
@@ -5941,6 +5941,7 @@ TEST_P(OEMCryptoUsageTableTest, ReloadUsageTableWithSkew) {
|
||||
vector<uint8_t> old_usage_header_2_ = encrypted_usage_header_;
|
||||
ASSERT_NO_FATAL_FAILURE(s.UpdateUsageEntry(&encrypted_usage_header_));
|
||||
vector<uint8_t> old_usage_header_1_ = encrypted_usage_header_;
|
||||
vector<uint8_t> old_usage_entry_1 = s.encrypted_usage_entry();
|
||||
ASSERT_NO_FATAL_FAILURE(s.UpdateUsageEntry(&encrypted_usage_header_));
|
||||
ASSERT_NO_FATAL_FAILURE(s.close());
|
||||
|
||||
@@ -5986,12 +5987,12 @@ TEST_P(OEMCryptoUsageTableTest, ReloadUsageTableWithSkew) {
|
||||
ASSERT_EQ(OEMCrypto_WARNING_GENERATION_SKEW,
|
||||
OEMCrypto_LoadUsageTableHeader(old_usage_header_1_.data(),
|
||||
old_usage_header_1_.size()));
|
||||
// Everything else should still work. Skew by 1 is just a warning.
|
||||
// Everything else should still work. The old entry goes with the old header.
|
||||
ASSERT_NO_FATAL_FAILURE(s.open());
|
||||
ASSERT_EQ(OEMCrypto_WARNING_GENERATION_SKEW,
|
||||
ASSERT_EQ(OEMCrypto_SUCCESS,
|
||||
OEMCrypto_LoadUsageEntry(s.session_id(), s.usage_entry_number(),
|
||||
s.encrypted_usage_entry().data(),
|
||||
s.encrypted_usage_entry().size()));
|
||||
old_usage_entry_1.data(),
|
||||
old_usage_entry_1.size()));
|
||||
ASSERT_NO_FATAL_FAILURE(InstallTestRSAKey(&s));
|
||||
ASSERT_EQ(OEMCrypto_SUCCESS, entry.license_messages().LoadResponse());
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user