OpenSSL Provider

this document provides information on configuring {{futurex}} {{k3}} with openssl providers using pkcs #11 libraries for additional questions related to your hsm, see the relevant administrator guide application description from the main latchset pkcs11 provider on github ( https //github com/latchset/pkcs11 provider) this is an openssl 3 x provider to access hardware and software tokens using the pkcs#11 cryptographic token interface access to tokens depends on loading an appropriate pkcs#11 driver that knows how to talk to the specific token the pkcs#11 provider is a connector that allows openssl to make proper use of such drivers this code targets pkcs#11 version 3 1 but is backwards compatible to version 3 0 and 2 40 as well why providers instead of engines openssl 3 x introduced a provider based architecture , replacing the old engine system from openssl 1 x feature openssl 1 x engine openssl 3 x provider integration manual registration, limited api support natively integrated, modular, supports openssl 3 x api hardware access requires engine specific code provides standardized pkcs#11 module access flexibility harder to maintain or extend easier to extend, multiple providers can coexist in short providers are modern, modular, and fully supported, making them the preferred method for pkcs#11 hsm integration why latchset pkcs11 provider direct integration with openssl 3 x provider api variety of successful integrations tested with futurex hsms supports pkcs#11 3 0+ tokens without extra libraries simplifies configuration compared to engines