198
edits
ModuleInterfaces: Difference between revisions
→In Error State
| Line 26: | Line 26: | ||
=== In Error State === | === In Error State === | ||
When the NSS cryptographic module is in the Error state, most PKCS #11 functions, including all the functions that output data via the data output interface, do nothing and return the CKR_DEVICE_ERROR error code immediately. Only the functions that shut down and restart the module, reinitialize the module, or output status information can be invoked in the Error state: FC_GetFunctionList, FC_Initialize, FC_Finalize, FC_GetInfo, FC_GetSlotList, FC_GetSlotInfo, FC_GetTokenInfo, FC_InitToken, FC_CloseSession, FC_CloseAllSessions, and FC_WaitForSlotEvent. | When the NSS cryptographic module is in the Error state, most PKCS #11 functions, including all the functions that output data via the data output interface, do nothing and return the CKR_DEVICE_ERROR error code immediately. The Error is tracked by a global boolean variable. Only the functions that shut down and restart the module, reinitialize the module, or output status information can be invoked in the Error state: FC_GetFunctionList, FC_Initialize, FC_Finalize, FC_GetInfo, FC_GetSlotList, FC_GetSlotInfo, FC_GetTokenInfo, FC_InitToken, FC_CloseSession, FC_CloseAllSessions, and FC_WaitForSlotEvent. All others check the state variable and, if true return immediately. | ||
=== During Self-Tests === | === During Self-Tests === | ||