OpenSSL Communities
Wed 11 Jun 2025 1:17AM

OpenSSL Library Binary Distributions and Installers for Microsoft Windows Poll

JB James Bourne Public Seen by 33

To discuss the poll and provide additional feedback regarding OpenSSL offering binary distributions and installers.

JB

Poll Created Wed 11 Jun 2025 12:23AM

OpenSSL Library Binary Distributions and Installers for Microsoft Windows You have until Mon 30 Jun 2025 1:00PM to participate.

What is this poll about?

Hello everyone. OpenSSL wishes to start delivering "reference" pre-compiled binaries and installers for Microsoft Windows. Traditionally, third parties have made these binary distributions and installers available. These binary distributions and installers were never vetted by OpenSSL and are often built by software vendors to meet their own needs or to cater to specific integrations. You can find a list of third- party builds here: https://github.com/openssl/openssl/wiki/Binaries

Why is this important?

Delivering reference pre-compiled binaries and installers to the community is important for the following reasons:

  1. They provide a reliable, tested, and digitally signed implementation of the OpenSSL Library

  2. Binaries and installers delivered by OpenSSL will provide end users and integrators with the confidence and veracity that they are fully functional, tested, defect-free, and free from malware

  3. Binaries and installers are built to meet community needs rather than those of specific software vendors

  4. The delivery of binaries and installers via direct download or package managers will give users of Microsoft Windows easy access to the OpenSSL Library which is not included in Microsoft Windows by default.

What are you asking people to do?

We would love for you to participate in our poll and tell us precisely what you want from our binary distributions and installers from a platform and feature perspective. The poll is straightforward. Simply rate the importance to you of each platform or feature that is to be included in OpenSSL's Binary Distributions and Installers for Microsoft Windows where 1 is unimportant and 5 is very mandatory. Feel free to provide any additional feedback regarding features you would like to see in the installers.

OpenSSL's Binary Distributions and Installers for Microsoft Windows Poll Results

Current results

Current results Option Points Mean Voters
Support for Intel/AMD 64-bit (x64) Windows Operating Systems 40 5.0 8
End User Build 39 4.9 8
FIPS Enabled 39 4.9 8
LTS and Interim Patch Versions 39 4.9 8
Microsoft Software Installer (MSI) 36 4.5 8
ZIP File For Portable / Custom Installations 33 4.1 8
Developer Build 32 4.0 8
Support for ARM64 (64-bit) Windows Operating Systems 29 3.6 8
Microsoft Universal C Runtime Dependency 27 3.4 8
AdvancedInstaller Installer (EXE) 27 3.4 8
Make Installers Available Via Package Managers 27 3.4 8
Support for Intel/AMD 32-bit (x86) Windows Operating Systems 22 2.8 8
Microsoft Visual C++ Redistributable Dependency 21 2.6 8
LTS Versions Only 17 2.1 8
Undecided 0 0 44

8 of 52 people have participated (15%)

TH

Tim Hudson Wed 11 Jun 2025 12:24AM

5 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Support for ARM64 (64-bit) Windows Operating Systems
5 - End User Build
5 - FIPS Enabled
5 - LTS and Interim Patch Versions
5 - Microsoft Software Installer (MSI)
5 - ZIP File For Portable / Custom Installations
3 - Developer Build
3 - Make Installers Available Via Package Managers
1 - Microsoft Visual C++ Redistributable Dependency
1 - Microsoft Universal C Runtime Dependency
1 - LTS Versions Only
1 - AdvancedInstaller Installer (EXE)

The vote is simply a reflection of Cryptsoft's customer base.

Note that the options don't actually include what we current use - which is a binary distribution with the libs and header files so you can develop code against it along with the DLLs and EXEs and with standard automatic configuration file handling - i.e. what a default build that would be done by a user from the source would result in. That is the combination which allows for both compiling and also distributing.

JB

James Bourne Wed 11 Jun 2025 12:24AM

5 - Make Installers Available Via Package Managers
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Microsoft Universal C Runtime Dependency
5 - Microsoft Software Installer (MSI)
5 - AdvancedInstaller Installer (EXE)
5 - ZIP File For Portable / Custom Installations
5 - Developer Build
5 - End User Build
5 - FIPS Enabled
5 - LTS and Interim Patch Versions
1 - Support for ARM64 (64-bit) Windows Operating Systems
1 - LTS Versions Only
1 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems
1 - Microsoft Visual C++ Redistributable Dependency

Based on our needs at firedaemon.com.

DH

Daniel Heinrich Wed 11 Jun 2025 12:24AM

5 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Support for ARM64 (64-bit) Windows Operating Systems
5 - End User Build
5 - FIPS Enabled
5 - LTS and Interim Patch Versions
5 - Microsoft Software Installer (MSI)
5 - ZIP File For Portable / Custom Installations
3 - Make Installers Available Via Package Managers
3 - AdvancedInstaller Installer (EXE)
2 - Developer Build
1 - Microsoft Visual C++ Redistributable Dependency
1 - Microsoft Universal C Runtime Dependency
1 - LTS Versions Only

In my opinion, distributing Windows binaries in this manner is the most effective approach.

PY

Paul Yang Wed 11 Jun 2025 12:24AM

5 - LTS and Interim Patch Versions
5 - Microsoft Visual C++ Redistributable Dependency
5 - Microsoft Software Installer (MSI)
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Microsoft Universal C Runtime Dependency
5 - End User Build
4 - FIPS Enabled
2 - Developer Build
1 - Make Installers Available Via Package Managers
1 - Support for ARM64 (64-bit) Windows Operating Systems
1 - LTS Versions Only
1 - AdvancedInstaller Installer (EXE)
1 - ZIP File For Portable / Custom Installations
1 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems

Most of the use cases I encountered in the small business aspect are end-user, instead of developers. Furthermore, a small software company that relies on OpenSSL to build their applications on Windows platform has always adequate heads to figure out how to compile the library into their products.

ML

Marc-Andre Lemburg Wed 11 Jun 2025 12:24AM

5 - Make Installers Available Via Package Managers
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Support for ARM64 (64-bit) Windows Operating Systems
5 - Developer Build
5 - End User Build
5 - FIPS Enabled
5 - LTS Versions Only
5 - LTS and Interim Patch Versions
5 - AdvancedInstaller Installer (EXE)
5 - ZIP File For Portable / Custom Installations
5 - Microsoft Visual C++ Redistributable Dependency
5 - Microsoft Software Installer (MSI)
3 - Microsoft Universal C Runtime Dependency
2 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems

We have been building such binaries for OpenSSL for Windows for a while in the past (for pyOpenSSL) and found this to be quite a bit of work, because OpenSSL often changed small details in every single release which required patching our build process. Having OpenSSL devs do this themselves will make them more aware of the need for such efforts and apply more care to not make things too complicated w/r to the Windows platform.

SD

Sangeeta Devi Wed 11 Jun 2025 12:24AM

5 - Make Installers Available Via Package Managers
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Microsoft Universal C Runtime Dependency
5 - Microsoft Software Installer (MSI)
5 - AdvancedInstaller Installer (EXE)
5 - ZIP File For Portable / Custom Installations
5 - Developer Build
5 - End User Build
5 - FIPS Enabled
5 - LTS and Interim Patch Versions
3 - Support for ARM64 (64-bit) Windows Operating Systems
1 - LTS Versions Only
1 - Microsoft Visual C++ Redistributable Dependency
1 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems

Based on FireDaemon's needs

JM

Jake Maynard Wed 11 Jun 2025 12:24AM

5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - Microsoft Universal C Runtime Dependency
5 - Support for ARM64 (64-bit) Windows Operating Systems
5 - Developer Build
5 - End User Build
5 - FIPS Enabled
5 - Microsoft Visual C++ Redistributable Dependency
4 - Make Installers Available Via Package Managers
4 - LTS and Interim Patch Versions
4 - ZIP File For Portable / Custom Installations
4 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems
4 - AdvancedInstaller Installer (EXE)
3 - LTS Versions Only
3 - Microsoft Software Installer (MSI)

It is important for the community to have a path to obtain signed builds from OpenSSL for supply chain integrity.

AK

Aditya Koranga Wed 11 Jun 2025 12:24AM

5 - Developer Build
5 - Support for Intel/AMD 64-bit (x64) Windows Operating Systems
5 - LTS and Interim Patch Versions
5 - FIPS Enabled
4 - End User Build
4 - Support for ARM64 (64-bit) Windows Operating Systems
4 - LTS Versions Only
3 - Support for Intel/AMD 32-bit (x86) Windows Operating Systems
3 - Microsoft Software Installer (MSI)
3 - AdvancedInstaller Installer (EXE)
3 - ZIP File For Portable / Custom Installations
2 - Microsoft Universal C Runtime Dependency
2 - Microsoft Visual C++ Redistributable Dependency
1 - Make Installers Available Via Package Managers

Based on my opinions.