Clone this repo:
  1. d18cb77 Fix d2i_X509_AUX. by David Benjamin · 2 days ago master
  2. 176dbf0 Check for malloc failure in r2i_certpol. by David Benjamin · 3 days ago
  3. 3bb5a77 Fix memory leak on error in BN_mpi2bn. by David Benjamin · 3 days ago
  4. 6f621bd Merge documentation from chromium's net/der into cbs.c by Nick Harper · 3 days ago version_for_cocoapods_3.0
  5. 992c20a Another OPENSSL_NO_THREADS build fix. 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.

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