Scroll to navigation

OPENCRYPTOKI(7) openCryptoki OPENCRYPTOKI(7)

NAME

openCryptoki - A PKCS#11 implementation.

DESCRIPTION

openCryptoki is an implementation of the PKCS#11 API standard. It provides an interface to the functions of underlying cryptographic tokens, which may be implemented via software or hardware. The PKCS#11 specification is maintained by OASIS. More information on PKCS#11 can be found on the OASIS website: https://www.oasis-open.org/committees/pkcs11/

openCryptoki implements PKCS#11 version 3.0 and partially versions 3.1 and 3.2.

Supported Platforms

openCryptoki runs on Linux on IBM Z (s390x), Linux on IBM Power (ppc64le), Linux on x86-64 (x86_64), Linux on ARM (aarch64), and AIX. Not all token backends are available on every platform; see the individual token descriptions below.

Token Backends

The following token backends are available:

A pure-software token using OpenSSL. Available on all supported platforms.
A token using the IBM libica library for hardware-accelerated cryptography. Only available on Linux on IBM Z (s390x).
A token using the IBM Common Cryptographic Architecture (CCA) library with IBM Crypto Express adapters. Available on Linux on IBM Z (s390x), Linux on IBM Power (ppc64le), Linux on x86-64, and AIX.
A token using IBM Crypto Express adapters configured with Enterprise PKCS#11 (EP11) firmware. Only available on Linux on IBM Z (s390x).
A token using the z/OS Integrated Cryptographic Service Facility (ICSF) via LDAP, for remote cryptographic operations on IBM Z. Available on Linux; not supported on AIX.
A token using a Trusted Platform Module (TPM 1.2 only). Available on Linux platforms where the TrouSerS stack is present. This token is deprecated and will be removed in a future release.

To use openCryptoki, run the pkcsslotd daemon. The daemon will read the opencryptoki.conf file to collect information about the tokens and their slots.

Use the pkcsconf utility to further configure openCryptoki once the daemon is running. The p11sak tool can be used to manage keys and certificates in a token repository. Mechanism usage statistics can be collected and displayed using the pkcsstats tool. Algorithm and key-strength policies can be configured via policy.conf and strength.conf.

SECURITY NOTE

All non-root users that require access to PKCS#11 tokens using openCryptoki must be assigned to the pkcs11 group to be able to communicate with the pkcsslotd daemon. Only fully trusted users should be granted membership in the group. Group members can block other openCryptoki users from accessing PKCS#11 tokens.

SEE ALSO

pkcsslotd(8),
pkcsconf(1),
p11sak(1),
pkcsstats(1),
pkcstok_migrate(1),
pkcstok_admin(1),
pkcshsm_mk_change(1),
opencryptoki.conf(5),
policy.conf(5),
strength.conf(5).
August 2026 3.28.0