canmove, Confirmed users
937
edits
ModuleInterfaces: Difference between revisions
Jump to navigation
Jump to search
→During Self-Tests
| Line 30: | Line 30: | ||
=== During Self-Tests === | === During Self-Tests === | ||
The NSS cryptographic module performs power-up self-tests in the <code>FC_Initialize</code> function. Since no PKCS #11 function (except <code>FC_GetFunctionList</code>) may be called | The NSS cryptographic module performs power-up self-tests in the <code>FC_Initialize</code> function. Since no other PKCS #11 function (except <code>FC_GetFunctionList</code>) may be called before <code>FC_Initialize</code> returns successfully, all data output via the data output interface is inhibited while <code>FC_Initialize</code> is performing the self-tests. | ||
== Disconnecting the Output Data Path From the Key Processes == | == Disconnecting the Output Data Path From the Key Processes == | ||
During key generation and key zeroization, the NSS cryptographic module may perform audit logging at Security Level 2, but the audit records do not contain sensitive information. The NSS cryptographic module doesn't return the function output arguments until key generation or key zeroization is finished. Therefore, the logical paths used by output data exiting the module are logically disconnected from the processes/threads performing key generation and key zeroization. | During key generation and key zeroization, the NSS cryptographic module may perform audit logging at Security Level 2, but the audit records do not contain sensitive information. The NSS cryptographic module doesn't return the function output arguments until key generation or key zeroization is finished. Therefore, the logical paths used by output data exiting the module are logically disconnected from the processes/threads performing key generation and key zeroization. | ||