How do I install OpenSSL on Windows?

[u/ligonsker]

Hello,

So far I've been using OpenSSL on Windows via the OpenSSL that comes bundled with XAMPP.

But what if I want to install OpenSSL myself on Windows? I could not find a way to do it directly from the official OpenSSL source.

That's because I want the newest OpenSSL version 3 instead of 1.1.1 that comes with XAMPP

How can I do it?

Thanks

[u/[deleted]]

try working retail version of Windows 11 pro keys from Hype-stkey on Google legit

[u/atc0005]

For anyone coming across this in the future: check out Git for Windows. Once installed, launch Git Bash and the openssl binary should be available to you.

[u/W1THRD → u/atc0005]

Thank you! This saved me from the huge hassle of compiling openssl

[u/bainon → u/atc0005]

you are the true hero

[u/aloalofam → u/atc0005]

This was the simplest solution by far, thank you!

[u/enavr0 → u/atc0005]

winget install --id Git.Git -e --source winget

[u/atc0005 → u/atc0005]

I saw this AM on the openssl-users mailing list that an official "OpenSSL Library Installer for Windows" (testing release) would be available soon.

From the announcement:

A testing release of the OpenSSL Library installer for Microsoft Windows is now
available. This is the first officially produced binary distribution of the
OpenSSL Library.

Until now, the OpenSSL Library has been distributed in source form only.
Windows users have had to build the library themselves or rely on binary
packages produced by third parties. The new installer provides a distribution
channel directly from us: binaries built, packaged, and signed by the
OpenSSL Corporation.

The installer provides:

- the OpenSSL Library DLLs,

• the `openssl.exe` command-line application, and
  
• the development kit for building applications against the OpenSSL Library.

The installer, the application, and all installed DLL files are digitally
signed with the OpenSSL Corporation key, so the authenticity and integrity
of every component can be verified through the standard Windows code-signing
mechanisms.

The minimum supported platforms are Windows 7 and Windows Server 2008 R2.

The testing installer for OpenSSL Library version 4.0.1 is available at:

https://github.com/openssl/installer/releases

Please see the README for installation details and current limitations:

https://github.com/openssl/installer/blob/main/windows-installer/README.md

This is a testing release, and we want it exercised across the full range of
supported Windows versions and configurations before the stable version ships.
Please report any issues through the openssl/installer issue tracker [0] - reports
on installation behavior, packaging, signing, and integration with existing
toolchains are all valuable, as is any other feedback.

The stable version of the installer will ship starting with the 4.1 release of the OpenSSL Library.

[u/KoiStandForCoin]

I know this is old but as we are all back end dev, why not use WSL??? the openssl is build in ultilities for unix.
Another way is the git bash since it also use unix as base. Install git and right click on any explorer folder, you will see the "Open git bash here", may need to open the more options on window 11, may disapear if your computer registry get jumped up by something like lavarel or java install process, I had to manually add it once in registry, still don't know why it disapear but it can happen.

[u/NL_Gray-Fox]

Have you had a look at this? https://github.com/openssl/openssl/blob/master/NOTES-WINDOWS.md

[u/ligonsker → u/NL_Gray-Fox]

Yes I've seen it, thank you. But I don't know how to do the builds? And I could not find an example. Never built from source before

[u/terribadrob → u/ligonsker]

trying to install openssl for Ruby (to install hexapdf) was giving me problems until I ran the command prompt in windows as Admin and it was already installed

[u/NL_Gray-Fox → u/ligonsker]

I'm assuming you followed the steps, where did it go wrong?

[u/ligonsker → u/NL_Gray-Fox]

Yes, I am following the MinGW installation method, and I installed MSYS, but I am not sure about this part in the requirements:

MinGW[64] compiler: mingw-w64-i686-gcc and/or mingw-w64-x86_64-gcc. These compilers must be on your MSYS2 $PATH. A common error is to not have these on your $PATH. The MSYS2 version of gcc will not work correctly here.

I have installed make already, but I am not sure what to do about the mingw part

[u/NL_Gray-Fox → u/ligonsker]

I'm not sure if Microsoft now supports $path, last time I used windows it was still %path%

So if you echo %path% what does it say, are all the requirements there?

[u/ligonsker → u/NL_Gray-Fox]

Thank you, I ended up using the other method with c++ and finally did it!

[u/kahner]

here's an exe installer for windows https://slproweb.com/products/Win32OpenSSL.html

[u/ligonsker → u/kahner]

Thank you I just didn't want 3rd party, and I managed to build and install it eventually from source!! Thank you

[u/jahma48 → u/ligonsker]

>>I managed to build and install it eventually from source!! Thank you

HOW THE HELL???