canmove, Confirmed users
937
edits
ModuleInterfaces: Difference between revisions
Jump to navigation
Jump to search
→PKCS #11
No edit summary |
|||
| Line 18: | Line 18: | ||
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 | The functions in the PKCS #11 API are listed in the table in the section Specification of Services of the [http://www.mozilla.org/projects/security/pki/nss/fips/secpolicy.pdf Security Policy]. | ||
== Inhibition of Data Output == | == Inhibition of Data Output == | ||