Lines Matching refs:HMAC

106  * o   HMAC
215      * Start the creation of an HMAC key, shared with another IKeymasterDevice implementation.  Any
217      * must be a TEE Keymaster as well.  The HMAC key used to MAC and verify authentication tokens
218      * (HardwareAuthToken, VerificationToken and ConfirmationToken all use this HMAC key) must be
224      * @return error ErrorCode::OK on success, ErrorCode::UNIMPLEMENTED if HMAC agreement is not
225      *         implemented (note that all 4.0::IKeymasterDevice HALS must implement HMAC agreement,
237      * Complete the creation of an HMAC key, shared with another IKeymasterDevice implementation.
239      * there must be a TEE IKeymasterDevice as well.  The HMAC key used to MAC and verify
250      * This method computes the shared 32-byte HMAC ``H'' as follows (all IKeymasterDevice instances
322      *         computed the same shared HMAC key.  The sharingCheck value is computed as follows:
324      *             sharingCheck = HMAC(H, "Keymaster HMAC Verification")
327      *         IKeymasterDevice instances don't match, clients must assume that HMAC agreement
933      *   o The HMAC field must validate correctly.
1043      * -- HMAC keys --
1045      * HMAC key operations must specify Tag::MAC_LENGTH in inParams.  The specified value must be a
1116      *   o The HMAC field must validate correctly.
1221      *   o The HMAC field must validate correctly.
1238      * check the confirmation token by computing the 32-byte HMAC-SHA256 over all of the