Using PKCS#11 API
PKCS
Public-Key Cryptography Standards - Industry-standard cryptography specifications.#11 defines an API model for managing key material and performing cryptographic operations.
The API model is provided to the app developers in the C header files (refer to Cryptographic Token Interface Cryptoki, v2.20).
Cryptographic device vendors implement these C header files and distribute the implementation as DLL(Windows) or SO(Linux) libraries. Security officer - UKC partition administrator role.
Unbound PKCS#11 Library
The CORE-specific implementation of PKCSPublic-Key Cryptography Standards - Industry-standard cryptography specifications.#11 API is provided in the following file.
|
OS |
File |
Directory |
|---|---|---|
|
Linux-RHel |
libekmpkcs11.so |
/usr/lib64/ |
|
Linux-Ubuntu |
libekmpkcs11.so |
/usr/lib/ |
|
Windows |
ekmpkcs11.dll |
C:\Program Files\Dyadic\ekm-client\bin\ |
|
Windows 32-bit |
ekmpkcs11.dll |
C:\Program Files\Dyadic\ekm-client\bin\x86\ |
Compliance, Objects and Mechanisms
- For the implementation compliance with the standard, refer to PKCS#11 Compliance and Extensions.
- For the supported objects and mechanisms, refer to Supported Key Types and Mechanisms.
Unbound and PKCS#11 Terms
UKC terms map to the PKCSPublic-Key Cryptography Standards - Industry-standard cryptography specifications.#11 terms as follows:
- UKC partition - refer to Tokens and Slots.
- UKC key name and description - refer to CKA_ID and CKA_LABEL.
-
Security officer - UKC partition administrator role. - refer to CKU_USER and CKU_SO.
Development
For examples of typical PKCSPublic-Key Cryptography Standards - Industry-standard cryptography specifications.#11 sessions refer to PKCS#11 Usage Guide - General Overview.