Download Openssl Latest Version for Mac Updated

Download Openssl Latest Version for Mac

Installing OpenSSL library on macOS Catalina

Whether you lot are building apps for just macOS or for cross-platform, if your app is using OpenSSL for crypto-works, you lot volition have to install OpenSSL library since macOS ships with LibreSSL. Furthermore, cross-platform cryptography in .Net Core and .Net 5 uses OpenSSL on macOS.

Installing OpenSSL library on macOS seems piece of cake at start, but in exercise can be a real pain in the back. Hither is my journey of installing OpenSSL 1.1.1g on macOS Catalina (ten.15.6) and making it reachable by my .Net Core apps. I tried to write complete and generalized instructions to be as applicative to more systems as possible. And I also avoided symbolic linking (ln -s) and install_name_tool, since for me those are concluding options.

Installing OpenSSL

First, open a terminal, and meet if OpenSSL is already installed:

          brew info openssl

If it's non installed, you'll meet "Not installed" amongst the showtime few lines of output. Or may be it's non the latest version. And so, install or update if necessary:

          mash install openssl
#or#
brew upgrade openssl

Check if the system sees the library direct:

          openssl version -a

This command prints the SSL library which exists start in the PATH surround variable, being LibreSSL or OpenSSL at some version. OpenSSL doesn't need beingness here to be reachable. But if you want this for some reason, follow the instructions below, otherwise jump to the Making OpenSSL Reachable section.

Run the command "mash info openssl" again:

Since OpenSSL is keg-but [ane], it has to exist referred from an environs variable, which is done by the printed instruction, which is the repeat 'export… line in the blood-red rectangle at higher up screenshot. Information technology may exist a flake different in your system, information technology's because information technology depends on its version. Copy/paste/run that line, so that necessary control volition be written to .profile file [2].

To see what is written to .profile file, if you wonder, run beneath command at domicile directory:

          nano .contour

Manually run the .profile file to eliminate logoff & logon at this time:

          source ~/.profile

Cheque if system sees information technology now:

          openssl version -a

It should now print the up-to-date OpenSSL.

Making OpenSSL Reachable

When an app wants to use a library, macOS searches several locations to find it. Nosotros have to find library path of OpenSSL and add it to DYLD_LIBRARY_PATH environs variable. For this purpose, run "mash info openssl" command once more.

The path in the red rectangle at higher up screenshot is the path where OpenSSL is installed. To take the library path we're looking for, just append /lib to information technology. We desire this library path to be added to aforementioned environment variable at every user logon. And we'll apply below control for this, just replace the …/lib path with the one you take.

          echo 'export DYLD_LIBRARY_PATH="/usr/local/Cellar/openssl@1.one/1.1.1g/lib:$DYLD_LIBRARY_PATH"' >> ~/.profile

Manually run the .profile file [2] to eliminate logoff & logon at this time:

          source ~/.profile

This should practice the trick normally. Simply I've read that on some systems apps still cannot discover OpenSSL library. And then, try running your OpenSSL app. If the app gives an mistake like "No usable version of libssl was found. Arrest trap: 6" or "PlatformNotSupportedException", you may accept to install or update libssh2. I didn't need it merely hither it is:

          brew install libssh2
#or#
brew upgrade libssh2

Since libssh2 is non keg-only [1], it will be readily accessible without adding information technology to whatever environment variable.

That's it! Now OpenSSL library should be reachable from any app. At least that'southward the mutual hope 😊 This was not the funniest matter I did so far, but it was necessary. And I wrote it down here to exist a reference for anybody.

I wish you installations funnier than this one 😁 Now I need some beer 🍺

Happy OpenSSLing!

Note [1]: For a software via brew to exist "keg-but" means information technology is installed in /usr/local/Cellar simply non linked into places like /usr/local/bin, /usr/local/lib. This means most tools will not find it.

Note [ii]: .profile file (or .bash_profile, .bash_login) is something similar to autoexec.bat on Windows. Bash looks for it, and reads and executes commands in it, at user's every logon.