ModuleInterfaces: Difference between revisions
mNo edit summary |
m (→PKCS #11) |
||
| Line 27: | Line 27: | ||
=== PKCS #11=== | === PKCS #11=== | ||
This defines NSS's PKCS#11 (Cryptoki) implementation. The API itself is considered to | This defines NSS's PKCS#11 (Cryptoki) implementation. The API itself is considered to define the top edge of the cryptographic boundary, i.e., all application and upper level library access to the FIPS module is through this API. | ||
Also included in this module is the FIPS PKCS#11 token. | Also included in this module is the FIPS PKCS#11 token and the crypto algorithm support library called freebl. The FIPS PKCS#11 token is a Cryptoki token designed specifically for FIPS, and allows applications using NSS to operate in a strictly FIPS-mode. | ||
=== CRMF=== | === CRMF=== | ||
Revision as of 22:40, 17 May 2006
This is a draft
Module Ports
This is a software-only implementation. All keys, encrypted data and control information are exchanged through calls to library functions.
Module Interfaces
S/MIME
Interfaces for S/MIME version 3 and PKCS#7 secure mail. Not part of the cryptographic boundary.
SSL/TLS
Interfaces for Secure Sockets Layer and Transport Layer Security. Not part of the cryptographic boundary.
Certificate
Used for high-level certificate calls, for example processing the parts of a certificate, and CRL management. Not part of cryptographic boundary.
Key
High-level private/public key calls. Includes retrieving information about the key, such as its strength. Not part of cryptographic boundary.
Crypto
Provides high-level access to hashing, signature, and verification operations. Not part of cryptographic boundary.
PKCS #12
Interface for PKCS #12, Personal Information Storage and Retrieval. Used to allow import/export of certificates and private keys in a secure manner. Below cryptographic boundary.
PKCS #11
This defines NSS's PKCS#11 (Cryptoki) implementation. The API itself is considered to define the top edge of the cryptographic boundary, i.e., all application and upper level library access to the FIPS module is through this API. Also included in this module is the FIPS PKCS#11 token and the crypto algorithm support library called freebl. The FIPS PKCS#11 token is a Cryptoki token designed specifically for FIPS, and allows applications using NSS to operate in a strictly FIPS-mode.
CRMF
Interfaces for CRMF/CMMF. Not part of cryptographic boundary.
JAR
Signed object interface. Not part of cryptographic boundary.