ModuleInterfaces: Difference between revisions

Jump to navigation Jump to search
No edit summary
Line 16: Line 16:


=== PKCS #11===
=== PKCS #11===
The logical interfaces of the NSS cryptpgraphic module consist of the PKCS #11 (Cryptoki) API. The API itself defines the cryptographic boundary, i.e., all access to the cryptographic module is through this API. The module has three PKCS #11 tokens: two tokens that implement the non-FIPS approved mode of operation, and one token that implements the FIPS Approved mode of operation. The FIPS PKCS #11 token is designed specifically for FIPS 140-2, and allows applications using the NSS cryptographic module to operate in a strictly FIPS mode.
The logical interfaces of the NSS cryptpgraphic module consist of the PKCS #11 (Cryptoki) API. The API itself defines the cryptographic boundary, i.e., all access to the cryptographic module is through this API. The module has three PKCS #11 tokens: two tokens that implement the non-FIPS Approved mode of operation, and one token that implements the FIPS Approved mode of operation. The FIPS PKCS #11 token is designed specifically for FIPS 140-2, and allows applications using the NSS cryptographic module to operate in a strictly FIPS mode.


The functions in the PKCS #11 API are listed in [http://wiki.mozilla.org/Section_C_Table_II Table II] of the Security Policy.
The functions in the PKCS #11 API are listed in [http://wiki.mozilla.org/Section_C_Table_II Table II] of the Security Policy.
canmove, Confirmed users
937

edits

Navigation menu