|Skip Navigation Links|
|Exit Print View|
|Developer's Guide to Oracle Solaris 11 Security Oracle Solaris 11.1 Information Library|
The components of the cryptographic framework are described as follows.
libpkcs11.so – The framework provides access through the RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki). Applications need to link to the libpkcs11.so library, which implements the RSA PKCS #11 of the standard.
Pluggable interface – The pluggable interface is the service provider interface (SPI) for PKCS #11 cryptographic services that are provided by Oracle Corporation and third-party developers. Providers are user-level libraries. Providers are implemented through encryption services that are available from either hardware or software.
pkcs11_softtoken.so – A private shared object that contains user-level cryptographic mechanisms that are provided by Oracle Corporation The pkcs11_softtoken(5) library implements the RSA PKCS #11 v2.11 of the standard.
pkcs11_kernel.so – The private shared object used to access kernel-level cryptographic mechanisms. pkcs11_kernel(5) implements the RSA PKCS#11 v2.11 specification. pkcs11_kernel.so offers a PKCS#11 user interface for cryptographic services that are plugged into the kernel's service provider interface.
/dev/crypto pseudo device driver – The private pseudo device driver for using kernel-level cryptographic mechanisms. This information is provided to avoid inadvertent deletion of the pseudo device driver.
Note - This interface is only available through a special contract with Oracle Corporation Send email to email@example.com for more information.
Oracle HW and SW cryptographic providers – Kernel-level cryptographic services that are provided by Oracle Corporation HW refers to hardware cryptographic services such as accelerator boards. SW refers to kernel modules that provide cryptographic services, such as an implementation of a cryptographic algorithm.
Kernel cryptographic framework daemon – The private daemon that is responsible for managing system resources for cryptographic operations. The daemon is also responsible for verifying cryptographic providers.
/dev/cryptoadm pseudo device driver – The private pseudo device driver used by cryptoadm(1M) for administering kernel-level cryptographic mechanisms. This information is provided to avoid inadvertent deletion of the pseudo device driver.
cryptoadm – A user-level command for administrators to manage cryptographic services. A typical cryptoadm task is listing cryptographic providers and their capabilities. Disabling and enabling cryptographic mechanisms according to security policy is also performed with cryptoadm.