Third-party Software

The output of this build is a shared object / DLL which is loaded when the application launches. This allows us to use the OpenSSL library already installed on a target platform.

cURL

cURL is used to provide the Credential Manager with the capability to communicate with the KeyScaler REST API via HTTP requests. cURL provides us with TLS secure communication between client and server as well as proxy support with basic auth.

We support the following versions of cURL when building Credential Manager.

The output of this build is a shared object / DLL which is loaded dynamically at runtime. This allows for an existing cURL library to be used on a platform.

ZLIB

ZLIB provides the ability to compress data. It is used to compress the DDK object (if configured at build time to do so).

https://github.com/madler/zlib

ZLIB version 1.2.8

This is built as a shared object / DLL and is dynamically loaded at runtime.

Mosquitto

Mosquitto is used to enable Credential Manager to communicate with KeyScaler using the MQTT protocol, a common protocol used in IoT devices. This replaces the use of the HTTP protocol.

Mosquitto version 1.4.11

https://www.mosquitto.org/

Note that Mosquitto does not support OpenSSL v3.x so, if building MQTT support into Credential Manager it must be built with OpenSSL v1.1.1u. Due to this we have the ability to disable MQTT support when building Credential Manager. MQTT support is not included in our default releases.

UUID-dev

UUID dev is used to generate universally unique identifiers in Credential Manager

UUID version 2.39.1

https://github.com/util-linux/util-linux/tree/master/libuuid

This is statically linked into the Credential Manager at build time. It is not loaded dynamically at runtime.

JSON C

JSON C is a library that programmatically generates JSON documents. This is required by TPM2TSS.

JSON C version 0.16

https://github.com/json-c/json-c

This is built as a shared object and is loaded dynamically at runtime, when TPM support is included in the Credential Manager build.

TPM2TSS

TPM2TSS enables Credential Manager to utilise a TPM, when available, to generate and seal secrets on a device, e.g., RSA private keys. This is utilised to securely store a private key on a device, backed by the trusted platform hardware module, when the device is generating an RSA key-pair.

This library is only included in Credential Manager for Linux. On Windows, TPM secured data is managed by utilising the Windows Certificate Store and the Microsoft Platform Crypto Provider.

TPM2TSS version 4.0.1

https://github.com/tpm2-software/tpm2-tss

TPM2TSS generates several shared object libraries which are loaded dynamically at runtime. These are shipped with our Installer as they are typically not available on a device.

TPM support is optional when building Credential Manager. If TPM support not compiled into the application these files will not be included in the installer.

RapidJSON

RapidJSON is used to programmatically generate JSON documents when building our messages to the KeyScaler, and also when creating metadata payloads that are sent to DDKG.

RapidJSON version 1.0.2

https://rapidjson.org/

Compiled into the Credential Manager.

TinyXML

TinyXML is used to programmatically create XML documents within the DDKG.

TinyXML version 2.6.2

https://sourceforge.net/projects/tinyxml

This is built and statically linked into the DDKG. We do not load this dynamically at runtime, it is compiled into the application.

GTest

GTest is used for unit testing of the Credential Manager source code.

GTest version 1.7.0

https://github.com/google/googletest

This is built as a shared object / DLL and is dynamically loaded when the unit tests are executed. Our makefile allows unit test compilation and execution by running make runtests.

DDKG Third Party Software

This page details the third party software that is required to build DDKG.

OpenSSL

OpenSSL is used to provide cryptographic functions to DDKG. It is a proven trusted implementation that has been used commercially for decades. We build our DDKG against OpenSSL FIPS 140 compliant algorithms to ensure FIPS compatibility where required.

We support the following versions of OpenSSL, however, we recommend using the latest OpenSSL v3.x.