Clone this repo:
  1. 7c075b9 Change ppc64le AES code for FIPS. by Adam Langley · 3 days ago master
  2. 68f84f5 Add missing dependencies on exe_and_shlib_deps by Tom Anderson · 20 hours ago
  3. 806e18c Define OPENSSL_UNUSED for __clang__ as well. by David Benjamin · 26 hours ago
  4. 59e1a81 Turn off clang-format in embed_test_data.go output. by David Benjamin · 28 hours ago
  5. e7d3922 Improve Curve25519 cswap x64 assembly by Andreas Auernhammer · 2 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.

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