Clone this repo:
  1. 03cae7a Keep EVP_CIPHER/EVP_MD lookup and do_all functions in sync by David Benjamin · 4 days ago master
  2. dedd23e aarch64: Add missing LR validation in 'vpaes_cbc_encrypt' by Tamas Petz · 11 days ago
  3. 66e61c5 Allow PKCS7_sign to work for signing kernel modules. by Adam Langley · 6 days ago
  4. f958727 Speed up constant-time base64 decoding. by David Benjamin · 6 days ago
  5. 4937f05 Unwind remnants of ASN1_TFLG_NDEF. by David Benjamin · 3 weeks 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: