Clone this repo:
  1. f5d6d24 Move cmac into the FIPS module boundary. by Adam Langley · 3 weeks ago master
  2. a928171 Use CMake's C/C++ version features. by David Benjamin · 3 days ago
  3. ac639b7 Update build tools. by David Benjamin · 3 days ago
  4. 1694627 Don't leave stray errors in the error queue in X509_print_ex. by David Benjamin · 3 days ago
  5. f7e2879 Switch to the CIPD version of CMake on Windows. by David Benjamin · 3 days ago


BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.

Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.

Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.

BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.

Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.

Project links:

There are other files in this directory which might be helpful: