OpenSSL 3.3, 3.0 LTS, 1.1.1 LTS Binaries for Microsoft Windows (2024)

Table of Contents

• About OpenSSL
• Download OpenSSL
• Installing OpenSSL
  • Windows Installer
  • Winget Package Manager
  • ZIP File
• OpenSSL Screenshot
• OpenSSL Documentation
• Checking SSL / TLS Certificate Validity with Certify One
• Compiling OpenSSL From Source
  • Release Policy
  • Source
  • Build Script
  • Compilation
• Integrating OpenSSL with Your Visual Studio Project
  • Sample Project
  • Additional Include Directories
  • Additional Library Directories
  • Additional Dependencies
  • Basic Troubleshooting
  • FireDaemon Professional Development Services
• Privilege Escalation Mitigation
• Compatibility and Support Matrix
• License, Warranty, and Support
• Acknowledgments
• Buy SSL / TLS Certificates

OpenSSL is a popular open-source, publicly available software library that provides a robust, full-featured set of cryptographic functions and tools to secure communications over computer networks. When we build and ship FireDaemon Certify One, FireDaemon Fusion, and FireDaemon Lozenge we try to ensure it contains the most recent version of OpenSSL. We thought it would be useful to make our OpenSSL Binary Distribution available to you to download and use free of charge. The key advantages of using our OpenSSL Binary Distribution for Microsoft Windows over others that are available are:

• No need to deploy various software tools to attempt to compile the source from scratch. Our build script is available for free too if you do want to compile OpenSSL yourself
• No external dependencies. There is no need to install or distribute the Visual C++ Redistributable Runtime (MSVC). There is an implicit dependency on the Windows Universal C Runtime (UCRT) which is included by default in all modern versions of Microsoft Windows
• Packaged for simple deployment and use case scenarios including standalone, embeddable, deployable, or portable
• Digitally signed with our Extended Validation (EV) code signing certificate to avoid Windows SmartScreen warnings, and increase trust by Sectigo's authentication and verification procedures on us: FireDaemon Technologies Limited and validatable binary integrity to meet your compliance requirements.

Below you will find pre-compiled OpenSSL executables (EXE) and libraries (DLL) for Microsoft Windows Operating Systems in the form of installer and ZIP files. OpenSSL can be used standalone or integrated into any Windows application. The installers, EXEs and DLLs are digitally signed with our Extended Validation (EV) code signing certificate. We do not have an EAR CCL ECCN for our Binary Distributions. This is intentional. You must seek independent legal advice before using/integrating/exporting our Binary Distributions in your products if you believe you are subject to export controls.

Windows Installer

You can download the Windows installers found in the "Download OpenSSL" section above. Installation is straightforward. OpenSSL is installed into the following file system locations. These locations are specified during the build and follow OpenSSL's conventions.

%PROGRAMFILES%\FireDaemon OpenSSL 3%PROGRAMFILES%\Common Files\FireDaemon SSL 3

FireDaemon-OpenSSL-x64-3.3.2.exe /exenoui /exelog fdopenssl3.log /qn /norestart REBOOT=ReallySuppress APPDIR="C:\Program Files\FireDaemon OpenSSL 3" ADJUSTSYSTEMPATHENV=yes

:: To uninstall at an elevated command prompt, first verify the product GUIDwmic product where name="FireDaemon OpenSSL 3" get IdentifyingNumber:: Then uninstall silently using msiexecmsiexec /x {F241B47B-C3EE-459C-A7CE-3FA2F08E7CDB} /quiet /noreboot:: You can also use the original FireDaemon OpenSSL installerFireDaemon-OpenSSL-x64-3.3.2.exe /x // /quiet:: Or uninstall using PowerShell$app = Get-WmiObject Win32_Product | where { $_.name -eq "FireDaemon OpenSSL 3" }$app.Uninstall()

Winget Package Manager

Instead of downloading and installing the Windows Installer, you can use the Microsoft package manager called winget. Winget is built into Windows 10 and 11 or can be installed manually. To install FireDaemon OpenSSL, simply open a command prompt on your computer then:

:: Search for FireDaemon OpenSSLwinget search FireDaemon.OpenSSL:: Show the FireDaemon OpenSSL package contentswinget show FireDaemon.OpenSSL:: Install FireDaemon OpenSSL interactivelywinget install FireDaemon.OpenSSL --interactive:: Install FireDaemon OpenSSL silently (default)winget install FireDaemon.OpenSSL --silent:: Show installed packageswinget list FireDaemon:: Uninstall FireDaemon OpenSSLwinget uninstall FireDaemon.OpenSSL

ZIP File

Instead of using the installer or package manager, you can download one of the ZIP files found in the "Download OpenSSL" section above.

1. Follow the instructions below if you have downloaded one of the ZIP files above and want to deploy OpenSSL manually (e.g. on the local hard disk or a USB drive for a portable installation)
2. Download the appropriate FireDaemon OpenSSL Binary Distribution ZIP file via the links above.
3. Unpack the contents of the folder found in the ZIP file to a temporary directory (e.g. C:\Temp)
4. Copy the contents (i.e. the files and directories contained within) of the x64folder or x86 folder to your target directory (e.g. C:\OpenSSL)
5. Copy the ssl folder and contents to the target directory (e.g. C:\OpenSSL).

The commands to copy the files correctly from the location where you unpacked the ZIP file (assuming C:\Temp) are as follows:

: For OpenSSL 1.1.1 LTScd C:\Temp\openssl-1.1: For OpenSSL 3.0 LTScd C:\Temp\openssl-3.0: For OpenSSL 3.3cd C:\Temp\openssl-3: Copy the binaries specific to your platform: Copy 64-bit binariesrobocopy x64 C:\OpenSSL /E: Or, copy 32-bit binaries. Don't copy both!robocopy x86 C:\OpenSSL /E: Copy the ssl folderrobocopy ssl C:\OpenSSL\ssl /E

C:\OpenSSL>dir /bbinincludelibssl

: You can set OPENSSL_HOME=%~dp0 in a batch script for portable installsset OPENSSL_HOME=C:\OpenSSLset OPENSSL_CONF=%OPENSSL_HOME%\ssl\openssl.cnfset PATH=%OPENSSL_HOME%\bin;%PATH%cd /d %OPENSSL_HOME%openssl version -a

To create a certificate signing request and private key using the same environment variables as above:

openssl genrsa -out server.key 4096openssl req -new -key server.key -out server.csr -sha256openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

Please refer to OpenSSL's documentation.

FireDaemon Certify One allows you to audit, check, inspect, and validate SSL / TLS certificates and certificate chains. Fortify also has a browser-based TLS Encryption Check Tool available.

Release Policy

Whenever we release an updated version of FireDaemon Fusion, FireDaemon Certify One, or OpenSSL gets updated with security fixes, we will provide the latest tagged version of the OpenSSL stable branch. The currently deployed OpenSSL library commit versions are listed underneath the download links above. Commit is described viz:

git describe --always --tag --long --first-parent --dirty

Source

We directly pull from OpenSSL's official GitHub repository.

Build Script

You can use our build script to create the binary distributions. The build script has the following dependencies:

• Visual Studio Community Edition
• Git for Windows
• Strawberry Perl.

Compilation

The actual command line to build OpenSSL is as follows (where %toolset% is VC-WIN32 and VC-WIN64A respectively):

perl ..\Configure %toolset% no-asm no-ssl3 no-zlib no-comp no-autoload-config --api=1.1.0 --prefix="%installdir%" --openssldir="%commoninstalldir%" -DOPENSSL_NO_DEPRECATED

To use the headers and libraries present in FireDaemon OpenSSL in your Visual Studio project, you will need to configure the properties of your project.

Sample Project

We have included a sample Visual Studio Project in the latest OpenSSL 3.3 ZIP file. The sample project can be found in the "projects" folder.

Additional Include Directories

Prepend "C:\Program Files\FireDaemon Open SSL 3\include"; to Property Pages -> C/C++ -> General -> Additional Include Directories in your project per the screenshot below adjusting the prepended path to suit your installation. In our case we use a pre-defined User Macro called OpenSslIncludeDir. You can also specify this path on the command line:

/I"C:\Program Files\FireDaemon OpenSSL 3\include"

Additional Library Directories

Prepend "C:\Program Files\FireDaemon Open SSL 3\lib"; to Property Pages -> Linker -> General -> Additional Library Directories in your project per the screenshot below adjusting the prepended path to suit your installation. In our case we use a pre-defined User Macro called OpenSslLibraryDir. You can also specify this path on the command line:

/LIBPATH:"C:\Program Files\FireDaemon OpenSSL 3\lib"

/DYNAMICBASE "libcrypto.lib" "libssl.lib" 

Basic Troubleshooting

If you run into issues compiling or linking FireDaemon OpenSSL please review the tips below to help you debug your project:

• Ensure you have setup your Visual Studio project properly per the previous section
• If you are compiling OpenSSL yourself, ensure you choose the correct target platform. For example ./configure <toolset> where <toolset> can be triplets including VC-WIN64A and Cygwin-x86_64. The complete list of toolsets can be found by typing perl ..\configure LIST
• Verify that the versions of libssl.lib and libcrypto.lib are correct by using dumpbin.exe which is available in the Windows SDK. dumpbin /ALL libssl.lib should refer to libssl-3.dll. dumpbin /ALL libcrypto.lib should refer to libcrypto-3.dll
• Use /VERBOSE when linking to verify the libraries found and used by the linker
• Use Dependencies to verify the dependencies of your built executable
• Ensure you build, rebuild, or clean your project to avoid stale dependencies, outdated object files, and other artifacts and detritus that may have accumulated in your project
• Double check, then triple check your compiler and linker command line to ensure your project is not referring to folders or directories that may contain other versions of OpenSSL libs and DLLs
• Use pre-defined User Macros in your project to ensure you are explicitly referencing the correct OpenSSL include, lib, and bindirectories (e.g. OpenSslIncludeDir, OpenSslLibDir, OpenSslBinDir).

FireDaemon Software Development Services

We offer a paid for, commercial software development services to assist you in building OpenSSL and integrating OpenSSL into your project or product. Please contact us for rates and availability.

When building OpenSSL, the build scripts bake the default location of the library (ie. the installation directory) and the SSL configuration into the final product. By default, OpenSSL automatically loads the SSL configuration file from the default file system location. This leads to an easily exploitable privilege escalation scenario documented in CVE-2019-12572. Our build of OpenSSL mitigates this flaw using the following preventative measures:

• The target directories we have chosen are Windows' default system program files directories assuming a 64-bit architecture with a shared configuration file directory common to both x64 and x86:
  • x64: C:\Program Files\FireDaemon OpenSSL, C:\Program Files\Common Files\FireDaemon SSL
  • x86: C:\Program Files (x86)\FireDaemon OpenSSL, C:\Program Files\Common Files\FireDaemon SSL
• To mitigate security holes even on non-default installations, we build the library such that it doesn't automatically load the SSL configuration. Hence, when using the OpenSSL tools or the DLLs in your products you have to explicitly load the SSL configuration.
• All FireDaemon software products that utilise OpenSSL initialise the OpenSSL library at runtime using a flag that prevents the loading of the default configuration.

The table below provides a compatibility and support matrix, mapping specific compatible Microsoft Windows operating system versions to specific FireDaemonOpenSSL software versions.

(1) Windows Desktop Operating System is End of Support

(2) Windows Server Operating System is End of Support

Our OpenSSL Binary Distribution is free to use and redistribute. Product use, redistribution, and warranty are governed by the OpenSSL License. If you have questions regarding OpenSSL, wish to report bugs, or require implementation guidance please consider joining the OpenSSL Community.

This product includes:

• Software developed by the OpenSSL Project for use in the OpenSSL Library
• Cryptographic software written by Eric Young
• Software written by Tim Hudson.