Esys_ClearControl.3 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253
  1. .TH "Esys_ClearControl" 3 "Fri Oct 7 2022" "Version 3.2.0" "tpm2-tss" \" -*- nroff -*-
  2. .ad l
  3. .nh
  4. .SH NAME
  5. Esys_ClearControl
  6. .SH SYNOPSIS
  7. .br
  8. .PP
  9. .SS "Functions"
  10. .in +1c
  11. .ti -1c
  12. .RI "TSS2_RC \fBEsys_ClearControl_Async\fP (\fBESYS_CONTEXT\fP *esysContext, \fBESYS_TR\fP auth, \fBESYS_TR\fP shandle1, \fBESYS_TR\fP shandle2, \fBESYS_TR\fP shandle3, TPMI_YES_NO disable)"
  13. .br
  14. .ti -1c
  15. .RI "TSS2_RC \fBEsys_ClearControl\fP (\fBESYS_CONTEXT\fP *esysContext, \fBESYS_TR\fP auth, \fBESYS_TR\fP shandle1, \fBESYS_TR\fP shandle2, \fBESYS_TR\fP shandle3, TPMI_YES_NO disable)"
  16. .br
  17. .ti -1c
  18. .RI "TSS2_RC \fBEsys_ClearControl_Finish\fP (\fBESYS_CONTEXT\fP *esysContext)"
  19. .br
  20. .ti -1c
  21. .RI "TSS2_RC \fBEsys_Clear\fP (\fBESYS_CONTEXT\fP *esysContext, \fBESYS_TR\fP authHandle, \fBESYS_TR\fP shandle1, \fBESYS_TR\fP shandle2, \fBESYS_TR\fP shandle3)"
  22. .br
  23. .ti -1c
  24. .RI "TSS2_RC \fBEsys_Clear_Finish\fP (\fBESYS_CONTEXT\fP *esysContext)"
  25. .br
  26. .in -1c
  27. .SH "Detailed Description"
  28. .PP
  29. ESAPI function to invoke the TPM2_ClearControl command either as a one-call or in an asynchronous manner\&.
  30. .SH "Function Documentation"
  31. .PP
  32. .SS "TSS2_RC Esys_Clear (\fBESYS_CONTEXT\fP * esysContext, \fBESYS_TR\fP authHandle, \fBESYS_TR\fP shandle1, \fBESYS_TR\fP shandle2, \fBESYS_TR\fP shandle3)"
  33. One-Call function for TPM2_Clear
  34. .PP
  35. This function invokes the TPM2_Clear command in a one-call variant\&. This means the function will block until the TPM response is available\&. All input parameters are const\&. The memory for non-simple output parameters is allocated by the function implementation\&.
  36. .PP
  37. \fBParameters:\fP
  38. .RS 4
  39. \fIesysContext\fP The \fBESYS_CONTEXT\fP\&.
  40. .br
  41. \fIauthHandle\fP TPM2_RH_LOCKOUT or TPM2_RH_PLATFORM+{PP}\&.
  42. .br
  43. \fIshandle1\fP Session handle for authorization of authHandle
  44. .br
  45. \fIshandle2\fP Second session handle\&.
  46. .br
  47. \fIshandle3\fP Third session handle\&.
  48. .RE
  49. .PP
  50. \fBReturn values:\fP
  51. .RS 4
  52. \fITSS2_RC_SUCCESS\fP if the function call was a success\&.
  53. .br
  54. \fITSS2_ESYS_RC_BAD_REFERENCE\fP if the esysContext or required input pointers or required output handle references are NULL\&.
  55. .br
  56. \fITSS2_ESYS_RC_BAD_CONTEXT\fP if esysContext corruption is detected\&.
  57. .br
  58. \fITSS2_ESYS_RC_MEMORY\fP if the ESAPI cannot allocate enough memory for internal operations or return parameters\&.
  59. .br
  60. \fITSS2_ESYS_RC_BAD_SEQUENCE\fP if the context has an asynchronous operation already pending\&.
  61. .br
  62. \fITSS2_ESYS_RC_INSUFFICIENT_RESPONSE\fP if the TPM's response does not at least contain the tag, response length, and response code\&.
  63. .br
  64. \fITSS2_ESYS_RC_MALFORMED_RESPONSE\fP if the TPM's response is corrupted\&.
  65. .br
  66. \fITSS2_ESYS_RC_RSP_AUTH_FAILED\fP if the response HMAC from the TPM did not verify\&.
  67. .br
  68. \fITSS2_ESYS_RC_MULTIPLE_DECRYPT_SESSIONS\fP if more than one session has the 'decrypt' attribute bit set\&.
  69. .br
  70. \fITSS2_ESYS_RC_MULTIPLE_ENCRYPT_SESSIONS\fP if more than one session has the 'encrypt' attribute bit set\&.
  71. .br
  72. \fITSS2_ESYS_RC_BAD_TR\fP if any of the ESYS_TR objects are unknown to the \fBESYS_CONTEXT\fP or are of the wrong type or if required ESYS_TR objects are ESYS_TR_NONE\&.
  73. .br
  74. \fITSS2_ESYS_RC_NO_DECRYPT_PARAM\fP if one of the sessions has the 'decrypt' attribute set and the command does not support encryption of the first command parameter\&.
  75. .br
  76. \fITSS2_ESYS_RC_NO_ENCRYPT_PARAM\fP if one of the sessions has the 'encrypt' attribute set and the command does not support encryption of the first response parameter\&.
  77. .br
  78. \fITSS2_RCs\fP produced by lower layers of the software stack may be returned to the caller unaltered unless handled internally\&.
  79. .RE
  80. .PP
  81. .SS "TSS2_RC Esys_Clear_Finish (\fBESYS_CONTEXT\fP * esysContext)"
  82. Asynchronous finish function for TPM2_Clear
  83. .PP
  84. This function returns the results of a TPM2_Clear command invoked via Esys_Clear_Finish\&. All non-simple output parameters are allocated by the function's implementation\&. NULL can be passed for every output parameter if the value is not required\&.
  85. .PP
  86. \fBParameters:\fP
  87. .RS 4
  88. \fIesysContext\fP The \fBESYS_CONTEXT\fP\&.
  89. .RE
  90. .PP
  91. \fBReturn values:\fP
  92. .RS 4
  93. \fITSS2_RC_SUCCESS\fP on success
  94. .br
  95. \fIESYS_RC_SUCCESS\fP if the function call was a success\&.
  96. .br
  97. \fITSS2_ESYS_RC_BAD_REFERENCE\fP if the esysContext or required input pointers or required output handle references are NULL\&.
  98. .br
  99. \fITSS2_ESYS_RC_BAD_CONTEXT\fP if esysContext corruption is detected\&.
  100. .br
  101. \fITSS2_ESYS_RC_MEMORY\fP if the ESAPI cannot allocate enough memory for internal operations or return parameters\&.
  102. .br
  103. \fITSS2_ESYS_RC_BAD_SEQUENCE\fP if the context has an asynchronous operation already pending\&.
  104. .br
  105. \fITSS2_ESYS_RC_TRY_AGAIN\fP if the timeout counter expires before the TPM response is received\&.
  106. .br
  107. \fITSS2_ESYS_RC_INSUFFICIENT_RESPONSE\fP if the TPM's response does not at least contain the tag, response length, and response code\&.
  108. .br
  109. \fITSS2_ESYS_RC_RSP_AUTH_FAILED\fP if the response HMAC from the TPM did not verify\&.
  110. .br
  111. \fITSS2_ESYS_RC_MALFORMED_RESPONSE\fP if the TPM's response is corrupted\&.
  112. .br
  113. \fITSS2_RCs\fP produced by lower layers of the software stack may be returned to the caller unaltered unless handled internally\&.
  114. .RE
  115. .PP
  116. .SS "TSS2_RC Esys_ClearControl (\fBESYS_CONTEXT\fP * esysContext, \fBESYS_TR\fP auth, \fBESYS_TR\fP shandle1, \fBESYS_TR\fP shandle2, \fBESYS_TR\fP shandle3, TPMI_YES_NO disable)"
  117. One-Call function for TPM2_ClearControl
  118. .PP
  119. This function invokes the TPM2_ClearControl command in a one-call variant\&. This means the function will block until the TPM response is available\&. All input parameters are const\&. The memory for non-simple output parameters is allocated by the function implementation\&.
  120. .PP
  121. \fBParameters:\fP
  122. .RS 4
  123. \fIesysContext\fP The \fBESYS_CONTEXT\fP\&.
  124. .br
  125. \fIauth\fP TPM2_RH_LOCKOUT or TPM2_RH_PLATFORM+{PP}\&.
  126. .br
  127. \fIshandle1\fP Session handle for authorization of auth
  128. .br
  129. \fIshandle2\fP Second session handle\&.
  130. .br
  131. \fIshandle3\fP Third session handle\&.
  132. .br
  133. \fIdisable\fP YES if the disableOwnerClear flag is to be SET, NO if the flag is to be CLEAR\&.\&.
  134. .RE
  135. .PP
  136. \fBReturn values:\fP
  137. .RS 4
  138. \fITSS2_RC_SUCCESS\fP if the function call was a success\&.
  139. .br
  140. \fITSS2_ESYS_RC_BAD_REFERENCE\fP if the esysContext or required input pointers or required output handle references are NULL\&.
  141. .br
  142. \fITSS2_ESYS_RC_BAD_CONTEXT\fP if esysContext corruption is detected\&.
  143. .br
  144. \fITSS2_ESYS_RC_MEMORY\fP if the ESAPI cannot allocate enough memory for internal operations or return parameters\&.
  145. .br
  146. \fITSS2_ESYS_RC_BAD_SEQUENCE\fP if the context has an asynchronous operation already pending\&.
  147. .br
  148. \fITSS2_ESYS_RC_INSUFFICIENT_RESPONSE\fP if the TPM's response does not at least contain the tag, response length, and response code\&.
  149. .br
  150. \fITSS2_ESYS_RC_MALFORMED_RESPONSE\fP if the TPM's response is corrupted\&.
  151. .br
  152. \fITSS2_ESYS_RC_RSP_AUTH_FAILED\fP if the response HMAC from the TPM did not verify\&.
  153. .br
  154. \fITSS2_ESYS_RC_MULTIPLE_DECRYPT_SESSIONS\fP if more than one session has the 'decrypt' attribute bit set\&.
  155. .br
  156. \fITSS2_ESYS_RC_MULTIPLE_ENCRYPT_SESSIONS\fP if more than one session has the 'encrypt' attribute bit set\&.
  157. .br
  158. \fITSS2_ESYS_RC_BAD_TR\fP if any of the ESYS_TR objects are unknown to the \fBESYS_CONTEXT\fP or are of the wrong type or if required ESYS_TR objects are ESYS_TR_NONE\&.
  159. .br
  160. \fITSS2_ESYS_RC_NO_DECRYPT_PARAM\fP if one of the sessions has the 'decrypt' attribute set and the command does not support encryption of the first command parameter\&.
  161. .br
  162. \fITSS2_ESYS_RC_NO_ENCRYPT_PARAM\fP if one of the sessions has the 'encrypt' attribute set and the command does not support encryption of the first response parameter\&.
  163. .br
  164. \fITSS2_RCs\fP produced by lower layers of the software stack may be returned to the caller unaltered unless handled internally\&.
  165. .RE
  166. .PP
  167. .SS "TSS2_RC Esys_ClearControl_Async (\fBESYS_CONTEXT\fP * esysContext, \fBESYS_TR\fP auth, \fBESYS_TR\fP shandle1, \fBESYS_TR\fP shandle2, \fBESYS_TR\fP shandle3, TPMI_YES_NO disable)"
  168. Asynchronous function for TPM2_ClearControl
  169. .PP
  170. This function invokes the TPM2_ClearControl command in a asynchronous variant\&. This means the function will return as soon as the command has been sent downwards the stack to the TPM\&. All input parameters are const\&. In order to retrieve the TPM's response call Esys_ClearControl_Finish\&.
  171. .PP
  172. \fBParameters:\fP
  173. .RS 4
  174. \fIesysContext\fP The \fBESYS_CONTEXT\fP\&.
  175. .br
  176. \fIauth\fP TPM2_RH_LOCKOUT or TPM2_RH_PLATFORM+{PP}\&.
  177. .br
  178. \fIshandle1\fP Session handle for authorization of auth
  179. .br
  180. \fIshandle2\fP Second session handle\&.
  181. .br
  182. \fIshandle3\fP Third session handle\&.
  183. .br
  184. \fIdisable\fP YES if the disableOwnerClear flag is to be SET, NO if the flag is to be CLEAR\&.\&.
  185. .RE
  186. .PP
  187. \fBReturn values:\fP
  188. .RS 4
  189. \fIESYS_RC_SUCCESS\fP if the function call was a success\&.
  190. .br
  191. \fITSS2_ESYS_RC_BAD_REFERENCE\fP if the esysContext or required input pointers or required output handle references are NULL\&.
  192. .br
  193. \fITSS2_ESYS_RC_BAD_CONTEXT\fP if esysContext corruption is detected\&.
  194. .br
  195. \fITSS2_ESYS_RC_MEMORY\fP if the ESAPI cannot allocate enough memory for internal operations or return parameters\&.
  196. .br
  197. \fITSS2_RCs\fP produced by lower layers of the software stack may be returned to the caller unaltered unless handled internally\&.
  198. .br
  199. \fITSS2_ESYS_RC_MULTIPLE_DECRYPT_SESSIONS\fP if more than one session has the 'decrypt' attribute bit set\&.
  200. .br
  201. \fITSS2_ESYS_RC_MULTIPLE_ENCRYPT_SESSIONS\fP if more than one session has the 'encrypt' attribute bit set\&.
  202. .br
  203. \fITSS2_ESYS_RC_BAD_TR\fP if any of the ESYS_TR objects are unknown to the \fBESYS_CONTEXT\fP or are of the wrong type or if required ESYS_TR objects are ESYS_TR_NONE\&.
  204. .br
  205. \fITSS2_ESYS_RC_NO_DECRYPT_PARAM\fP if one of the sessions has the 'decrypt' attribute set and the command does not support encryption of the first command parameter\&.
  206. .br
  207. \fITSS2_ESYS_RC_NO_ENCRYPT_PARAM\fP if one of the sessions has the 'encrypt' attribute set and the command does not support encryption of the first response parameter\&.
  208. .RE
  209. .PP
  210. .SS "TSS2_RC Esys_ClearControl_Finish (\fBESYS_CONTEXT\fP * esysContext)"
  211. Asynchronous finish function for TPM2_ClearControl
  212. .PP
  213. This function returns the results of a TPM2_ClearControl command invoked via Esys_ClearControl_Finish\&. All non-simple output parameters are allocated by the function's implementation\&. NULL can be passed for every output parameter if the value is not required\&.
  214. .PP
  215. \fBParameters:\fP
  216. .RS 4
  217. \fIesysContext\fP The \fBESYS_CONTEXT\fP\&.
  218. .RE
  219. .PP
  220. \fBReturn values:\fP
  221. .RS 4
  222. \fITSS2_RC_SUCCESS\fP on success
  223. .br
  224. \fIESYS_RC_SUCCESS\fP if the function call was a success\&.
  225. .br
  226. \fITSS2_ESYS_RC_BAD_REFERENCE\fP if the esysContext or required input pointers or required output handle references are NULL\&.
  227. .br
  228. \fITSS2_ESYS_RC_BAD_CONTEXT\fP if esysContext corruption is detected\&.
  229. .br
  230. \fITSS2_ESYS_RC_MEMORY\fP if the ESAPI cannot allocate enough memory for internal operations or return parameters\&.
  231. .br
  232. \fITSS2_ESYS_RC_BAD_SEQUENCE\fP if the context has an asynchronous operation already pending\&.
  233. .br
  234. \fITSS2_ESYS_RC_TRY_AGAIN\fP if the timeout counter expires before the TPM response is received\&.
  235. .br
  236. \fITSS2_ESYS_RC_INSUFFICIENT_RESPONSE\fP if the TPM's response does not at least contain the tag, response length, and response code\&.
  237. .br
  238. \fITSS2_ESYS_RC_RSP_AUTH_FAILED\fP if the response HMAC from the TPM did not verify\&.
  239. .br
  240. \fITSS2_ESYS_RC_MALFORMED_RESPONSE\fP if the TPM's response is corrupted\&.
  241. .br
  242. \fITSS2_RCs\fP produced by lower layers of the software stack may be returned to the caller unaltered unless handled internally\&.
  243. .RE
  244. .PP
  245. .SH "Author"
  246. .PP
  247. Generated automatically by Doxygen for tpm2-tss from the source code\&.