Deploying Your TaurusTLS Applications

TaurusTLS relies on OpenSSL 3.x or 4.x. Depending on the target platform, OpenSSL is either linked dynamically (requiring DLLs) or statically (compiled into your executable).

You can download the correct binaries for all platforms here: OpenSSL-Distribution Releases

Dynamic Linking

Linux

TaurusTLS uses dynamic linking for the Linux64 platform. On Linux, OpenSSL is usually installed by default on the OS. We recommend explicitly documenting this dependency for your end-users. If you choose to deploy a specific version, you can download redistributable Linux package from the OpenSSL-Distribution Releases and redistribute it with your application(s).

Windows

On Windows, TaurusTLS uses Dynamic Linking. You must redistribute the OpenSSL shared libraries (.dll`) and the License file alongside your application executable.

Platforms and files you need to deploy.
Platform OpenSSL 3.x Required Files OpenSSL 4.x Required Files
Windows 32-bit libcrypto-3.dll, libssl-3.dll, LICENSE.txt libcrypto-4.dll, libssl-4.dll, LICENSE.txt
Windows 64-bit libcrypto-3-x64.dll, libssl-3-x64.dll, LICENSE.txt libcrypto-4-x64.dll, libssl-4-x64.dll, LICENSE.txt
Windows ARM64EC libcrypto-3-arm64.dll, libssl-3-arm64.dll, LICENSE.txt libcrypto-4-arm64.dll, libssl-4-arm64.dll, LICENSE.txt

Note: We strongly recommend also redistributing the openssl.exe included in the package, as users may need it for certificate management tasks like:

There's a reference book called the OpenSSL Cookbook.

Static Linking (Android, iOS, macOS)

On Mobile and macOS platforms, TaurusTLS uses Static Linking. The OpenSSL code is compiled directly into your application binary.