Searched refs:authorizations (Results 1 – 4 of 4) sorted by relevance
124 * caller-provided authorizations into two lists, those it enforces in hardware and those it does126 * the KeyCharacteristics struct. The IKeymasterDevice must also add the following authorizations334 * Verify authorizations for another IKeymasterDevice instance.337 * to ask the TEE IKeymasterDevice to verify authorizations for a key hosted in StrongBox.342 * authorizations it can and return those it validated in the VerificationToken. If it cannot351 * @param parametersToVerify Set of authorizations to verify. The caller may provide an empty388 * of a key in any way inconsistent with the authorizations specified at generation time. With903 * the key authorizations. If the specified purpose does not match, begin() must return967 * digest and padding, which means that the key authorizations need to contain the specified1025 * Tag::MIN_MAC_LENGTH in the key authorizations. For MAC lengths greater than 128 or[all …]
1275 * VerificationToken enables one Keymaster instance to validate authorizations for another. See
40 * authorizations.
1548 auto authorizations = AuthorizationSetBuilder() in TEST_P() local1556 ASSERT_EQ(ErrorCode::OK, GenerateKey(authorizations)); in TEST_P()