Esys_PolicyNameHash(3)
π
Esys_PolicyNameHash β from the Library Functions Manual bestie files β¨
Okay so real talk, this is the page for Esys_PolicyNameHash(3), and it's all about the ESAPI wrapper for the TPM2_PolicyNameHash command. TPM stuff can look scary but it's actually giving very structured, very slay energy once you get the rhythm. Let's go π«Ά
π NAME π
Esys_PolicyNameHash β the ESAPI function for the TPM2_PolicyNameHash command. That's it, that's the whole vibe check π
πΈ SYNOPSIS πΈ
β¨ Functions β¨
Here's the trio, bestie β three functions, all TSS2_RC returning, all iconic in their own way:
TSS2_RC Esys_PolicyNameHash_Async (ESYS_CONTEXT *esysContext, ESYS_TR
policySession, ESYS_TR shandle1, ESYS_TR shandle2, ESYS_TR shandle3,
const TPM2B_DIGEST *nameHash)
TSS2_RC Esys_PolicyNameHash (ESYS_CONTEXT *esysContext, ESYS_TR
policySession, ESYS_TR shandle1, ESYS_TR shandle2, ESYS_TR shandle3,
const TPM2B_DIGEST *nameHash)
TSS2_RC Esys_PolicyNameHash_Finish (ESYS_CONTEXT *esysContext)
π¦ Detailed Description π¦
So this is the ESAPI function that invokes the TPM2_PolicyNameHash command β and you can hit it either as a one-call situation or in an asynchronous manner. Pick your fighter, both are valid π
π Function Documentation π
π TSS2_RC Esys_PolicyNameHash (ESYS_CONTEXT * esysContext, ESYS_TR policySession, ESYS_TR shandle1, ESYS_TR shandle2, ESYS_TR shandle3, const TPM2B_DIGEST * nameHash)
One-Call function for TPM2_PolicyNameHash β the "just do it and wait" option, and honestly? Main character energy.
This function invokes the TPM2_PolicyNameHash command in a one-call variant. Translation: the function will block until the TPM response is available. No running off, no leaving you on read β it waits for the reply, periodt. All input parameters are const. The memory for non-simple output parameters is allocated by the function implementation. π
πΈ Parameters πΈ
esysContextβ TheESYS_CONTEXT. The whole context situation.policySessionβ Handle for the policy session being extended. We're growing the policy, bestie π§shandle1β First session handle.shandle2β Second session handle.shandle3β Third session handle.nameHashβ The digest to be added to the policy. The star of the show β¨
π Return values π
TSS2_RC_SUCCESSβ if the function call was a success. We love a clean win πTSS2_ESYS_RC_BAD_REFERENCEβ if theesysContextor required input pointers or required output handle references areNULL.TSS2_ESYS_RC_BAD_CONTEXTβ ifesysContextcorruption is detected.TSS2_ESYS_RC_MEMORYβ if the ESAPI cannot allocate enough memory for internal operations or return parameters.TSS2_ESYS_RC_BAD_SEQUENCEβ if the context has an asynchronous operation already pending.TSS2_ESYS_RC_INSUFFICIENT_RESPONSEβ if the TPM's response does not at least contain the tag, response length, and response code.TSS2_ESYS_RC_MALFORMED_RESPONSEβ if the TPM's response is corrupted.TSS2_ESYS_RC_RSP_AUTH_FAILEDβ if the response HMAC from the TPM did not verify.TSS2_ESYS_RC_MULTIPLE_DECRYPT_SESSIONSβ if more than one session has the'decrypt'attribute bit set.TSS2_ESYS_RC_MULTIPLE_ENCRYPT_SESSIONSβ if more than one session has the'encrypt'attribute bit set.TSS2_ESYS_RC_BAD_TRβ if any of theESYS_TRobjects are unknown to theESYS_CONTEXTor are of the wrong type or if requiredESYS_TRobjects areESYS_TR_NONE.TSS2_ESYS_RC_NO_DECRYPT_PARAMβ if one of the sessions has the'decrypt'attribute set and the command does not support encryption of the first command parameter.TSS2_ESYS_RC_NO_ENCRYPT_PARAMβ if one of the sessions has the'encrypt'attribute set and the command does not support encryption of the first response parameter.TSS2_RCsproduced by lower layers of the software stack may be returned to the caller unaltered unless handled internally. Lowkey the layers below you doing their own thing, and that's fine π
π¦ TSS2_RC Esys_PolicyNameHash_Async (ESYS_CONTEXT * esysContext, ESYS_TR policySession, ESYS_TR shandle1, ESYS_TR shandle2, ESYS_TR shandle3, const TPM2B_DIGEST * nameHash)
Asynchronous function for TPM2_PolicyNameHash β the "send it and dip" version, and ngl it's giving efficiency β¨
This function invokes the TPM2_PolicyNameHash command in an asynchronous variant. Which means: the function will return as soon as the command has been sent downwards the stack to the TPM. It does not wait around for the reply β she has places to be. All input parameters are const. In order to retrieve the TPM's response, call Esys_PolicyNameHash_Finish. Don't forget the finish, bestie, or you'll be left wondering π
πΈ Parameters πΈ
esysContextβ TheESYS_CONTEXT.policySessionβ Handle for the policy session being extended.shandle1β First session handle.shandle2β Second session handle.shandle3β Third session handle.nameHashβ The digest to be added to the policy.
π Return values π
ESYS_RC_SUCCESSβ if the function call was a success.TSS2_ESYS_RC_BAD_REFERENCEβ if theesysContextor required input pointers or required output handle references areNULL.TSS2_ESYS_RC_BAD_CONTEXTβ ifesysContextcorruption is detected.TSS2_ESYS_RC_MEMORYβ if the ESAPI cannot allocate enough memory for internal operations or return parameters.TSS2_RCsproduced by lower layers of the software stack may be returned to the caller unaltered unless handled internally.TSS2_ESYS_RC_MULTIPLE_DECRYPT_SESSIONSβ if more than one session has the'decrypt'attribute bit set.TSS2_ESYS_RC_MULTIPLE_ENCRYPT_SESSIONSβ if more than one session has the'encrypt'attribute bit set.TSS2_ESYS_RC_BAD_TRβ if any of theESYS_TRobjects are unknown to theESYS_CONTEXTor are of the wrong type or if requiredESYS_TRobjects areESYS_TR_NONE.TSS2_ESYS_RC_NO_DECRYPT_PARAMβ if one of the sessions has the'decrypt'attribute set and the command does not support encryption of the first command parameter.TSS2_ESYS_RC_NO_ENCRYPT_PARAMβ if one of the sessions has the'encrypt'attribute set and the command does not support encryption of the first response parameter.
π§ TSS2_RC Esys_PolicyNameHash_Finish (ESYS_CONTEXT * esysContext)
Asynchronous finish function for TPM2_PolicyNameHash β the reunion episode π¬
This function returns the results of a TPM2_PolicyNameHash command invoked via Esys_PolicyNameHash_Finish. All non-simple output parameters are allocated by the function's implementation. And here's a cute little detail: NULL can be passed for every output parameter if the value is not required. Skip what you don't need, no pressure π
πΈ Parameters πΈ
esysContextβ TheESYS_CONTEXT. That's the whole list, she's low maintenance.
π Return values π
TSS2_RC_SUCCESSβ on success.ESYS_RC_SUCCESSβ if the function call was a success.TSS2_ESYS_RC_BAD_REFERENCEβ if theesysContextor required input pointers or required output handle references areNULL.TSS2_ESYS_RC_BAD_CONTEXTβ ifesysContextcorruption is detected.TSS2_ESYS_RC_MEMORYβ if the ESAPI cannot allocate enough memory for internal operations or return parameters.TSS2_ESYS_RC_BAD_SEQUENCEβ if the context has an asynchronous operation already pending.TSS2_ESYS_RC_TRY_AGAINβ if the timeout counter expires before the TPM response is received. (Not a fail, just a "girl, try again" π₯)TSS2_ESYS_RC_INSUFFICIENT_RESPONSEβ if the TPM's response does not at least contain the tag, response length, and response code.TSS2_ESYS_RC_RSP_AUTH_FAILEDβ if the response HMAC from the TPM did not verify.TSS2_ESYS_RC_MALFORMED_RESPONSEβ if the TPM's response is corrupted.TSS2_RCsproduced by lower layers of the software stack may be returned to the caller unaltered unless handled internally.
β Author β
Generated automatically by Doxygen for tpm2-tss from the source code. So no human author to credit here β Doxygen did that, and honestly? It ate π
π Okay that's the whole page! Go extend that policy, bestie. You got this. π¦
Big sparkly sign-off energy: this cutie page came from tpm2-tss, Version 4.1.5, and it's filed under Esys_PolicyNameHash(3) π No cap, that's the version info, keep it for your records πβ¨
π¦ where this page comes from
- fedora 44: tpm2-tss-devel 4.1.5-1.fc44 Β· BSD-2-Clause
- fedora 44: tpm2-tss-devel 4.1.5-1.fc44 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms