LibreSSL is a fork of OpenSSL 1.0.1g developed by the OpenBSD project. Our goal is to modernize the codebase, improve security, and apply best practice development processes from OpenBSD.
LibreSSL is API compatible with OpenSSL 1.0.1, but does not yet include all new APIs from OpenSSL 1.0.2 and later. LibreSSL also includes APIs not yet present in OpenSSL. The current common API subset is OpenSSL 1.0.1.
LibreSSL is not ABI compatible with any release of OpenSSL, or necessarily earlier releases of LibreSSL. You will need to relink your programs to LibreSSL in order to use it, just as in moving between major versions of OpenSSL. LibreSSL's installed library version numbers are incremented to account for ABI and API changes.
While primarily developed on and taking advantage of APIs available on OpenBSD, the LibreSSL portable project attempts to provide working alternatives for other operating systems, and assists with improving OS-native implementations where possible.
At the time of this writing, LibreSSL is known to build and work on:
LibreSSL also supports the following Windows environments:
Official release tarballs are available at your friendly neighborhood OpenBSD mirror in directory LibreSSL, although we suggest that you use a mirror.
The LibreSSL portable build framework is also mirrored on GitHub.
Please report bugs either to the public libressl@openbsd.org mailing list, or to the GitHub issue tracker
Severe vulnerabilities or bugs requiring coordination with OpenSSL can be sent to the core team at libressl-security@openbsd.org.
If you have checked this source using Git, or have downloaded a source tarball from Github, follow these initial steps to prepare the source tree for building. Note: Your build will fail if you do not follow these instructions! If you cannot follow these instructions (e.g. Windows system using CMake) or cannot meet these prerequistes, please download an official release distribution from https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/ instead. Using official releases is strongly advised if you are not a developer.
./autogen.sh
to prepare the source tree for building or
run ./dist.sh
to prepare a tarball.Once you have a source tree, either by downloaded using git and having
run the autogen.sh
script above, or by downloading a release distribution from
an OpenBSD mirror, run these commands to build and install the package on most
systems:
./configure # see ./configure --help for configuration options
make check # runs builtin unit tests
make install # set DESTDIR= to install to an alternate location
If you wish to use the CMake build system, use these commands:
mkdir build
cd build
cmake ..
make
make test
For faster builds, you can use Ninja as well:
mkdir build-ninja
cd build-ninja
cmake -G"Ninja" ..
ninja
ninja test
Set the UNIX_STD environment variable to 2003
before running configure
in order to build with the HP C/aC++ compiler. See the "standards(5)" man
page for more details.
export UNIX_STD=2003
./configure
make
LibreSSL builds against relatively recent versions of Mingw-w64, not to be confused with the original mingw.org project. Mingw-w64 3.2 or later should work. See README.windows for more information
LibreSSL builds using the CMake target "Visual Studio 12 2013" and newer. To generate a Visual Studio project, install CMake, enter the LibreSSL source directory and run:
mkdir build-vs2013
cd build-vs2013
cmake -G"Visual Studio 12 2013" ..
Replace "Visual Studio 12 2013" with whatever version of Visual Studio you have installed. This will generate a LibreSSL.sln file that you can incorporate into other projects or build by itself.
Option Name | Default | Description |
---|---|---|
LIBRESSL_SKIP_INSTALL | OFF | allows skipping install() rules. Can be specified from command line using -DLIBRESSL_SKIP_INSTALL=ON |
LIBRESSL_APPS | ON | allows skipping application builds. Apps are required to run tests |
LIBRESSL_TESTS | ON | allows skipping of tests. Tests are only available in static builds |
BUILD_SHARED_LIBS | OFF | CMake option for building shared libraries. |
ENABLE_ASM | ON | builds assembly optimized rules. |
ENABLE_EXTRATESTS | OFF | Enable extra tests that may be unreliable on some platforms |
ENABLE_NC | OFF | Enable installing TLS-enabled nc(1) |
OPENSSLDIR | Blank | Set the default openssl directory. Can be specified from command line using -DOPENSSLDIR=<dirname> |
Make a new folder in your project root (where your main CMakeLists.txt file is located) called CMake. Copy the FindLibreSSL.cmake file to that folder, and add the following line to your main CMakeLists.txt:
set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/CMake;${CMAKE_MODULE_PATH}")
After your add_executable or add_library line in your CMakeLists.txt file add the following:
find_package(LibreSSL REQUIRED)
It will tell CMake to find LibreSSL and if found will let you use the following 3 interfaces in your CMakeLists.txt file:
If you for example want to use the LibreSSL TLS library in your test program, include it like so (SSL and Cryto are required by TLS and included automatically too):
target_link_libraries(test LibreSSL::TLS)
Full example:
cmake_minimum_required(VERSION 3.10.0)
set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/CMake;${CMAKE_MODULE_PATH}")
project(test)
add_executable(test Main.cpp)
find_package(LibreSSL REQUIRED)
target_link_libraries(test LibreSSL::TLS)
Following the guide in the sections above to compile LibreSSL using make and running "sudo make install" will install LibreSSL to the /usr/local/ folder, and will found automatically by find_package. If your system installs it to another location or you have placed them yourself in a different location, you can set the CMake variable LIBRESSL_ROOT_DIR to the correct path, to help CMake find the library.
Placing the library files in C:/Program Files/LibreSSL/lib and the include files in C:/Program Files/LibreSSL/include should let CMake find them automatically, but it is recommended that you use CMake-GUI to set the paths. It is more convenient as you can have the files in any folder you choose.