Esys_SequenceComplete(3)

✨ NAME ✨

Esys_SequenceComplete — it's literally the ESAPI function for the TPM2_SequenceComplete command, bestie. No cap.

This page is coming at you from the Library Functions Manual and it's about to be your new fave. 💅

---

✨ SYNOPSIS ✨

Functions

TSS2_RC Esys_SequenceComplete_Finish (ESYS_CONTEXT *esysContext,
    TPM2B_DIGEST **result, TPMT_TK_HASHCHECK **validation)

---

✨ Detailed Description ✨

Okay so, this is the ESAPI function that lets you invoke the TPM2_SequenceComplete command — and you've got options, bestie. You can do it as a one-call situation (all at once, iconic) or in an asynchronous manner (async vibes, very main character energy). Whatever works for your flow. ✨

---

✨ Function Documentation ✨

TSS2_RC Esys_SequenceComplete_Finish (ESYS_CONTEXT * esysContext, TPM2B_DIGEST ** result, TPMT_TK_HASHCHECK ** validation)

Asynchronous finish function for TPM2_SequenceComplete. This function returns the results of a TPM2_SequenceComplete command invoked via Esys_SequenceComplete_Finish. All non-simple output parameters are allocated by the function's implementation. And here's the tea: NULL can be passed for every output parameter if the value is not required — so you don't have to take everything if you don't need it. 🫶

Parameters

• esysContext — The ESYS_CONTEXT. That's your context, bestie. ✨
• result — The returned HMAC or digest in a sized buffer. (callee-allocated)
• validation — TPM2_Ticket indicating that the sequence of octets used to compute outDigest did not start with TPM2_GENERATED_VALUE. (callee-allocated)

Return values

• TSS2_RC_SUCCESS — on success 🎉
• ESYS_RC_SUCCESS — if the function call was a success. Slay. ✨
• TSS2_ESYS_RC_BAD_REFERENCE — if the esysContext or required input pointers or required output handle references are NULL. (not the vibe)
• TSS2_ESYS_RC_BAD_CONTEXT — if esysContext corruption is detected. Uh oh.
• TSS2_ESYS_RC_MEMORY — if the ESAPI cannot allocate enough memory for internal operations or return parameters. Memory issues, no cap.
• TSS2_ESYS_RC_BAD_SEQUENCE — if the context has an asynchronous operation already pending. Wait your turn, bestie.
• TSS2_ESYS_RC_TRY_AGAIN — if the timeout counter expires before the TPM response is received. Try again, it's giving patience.
• TSS2_ESYS_RC_INSUFFICIENT_RESPONSE — if the TPM's response does not at least contain the tag, response length, and response code. That's not enough info, periodt.
• TSS2_ESYS_RC_RSP_AUTH_FAILED — if the response HMAC from the TPM did not verify. Authentication said no. 🚫
• TSS2_ESYS_RC_MALFORMED_RESPONSE — if the TPM's response is corrupted. Corrupted? Not on my watch. 💀
• TSS2_RCs — produced by lower layers of the software stack may be returned to the caller unaltered unless handled internally. iykyk

---

✨ Author ✨

Generated automatically by Doxygen for tpm2-tss from the source code. It's giving auto-generated realness. 🤖✨

---

That's a wrap, bestie! This page is from tpm2-tss and it's Version 4.1.5. Stay iconic. 💖🎀🦋