Clone this repo:
  1. a5eafaa Restore mac_arm64_bazel by David Benjamin · 34 hours ago main
  2. 2215589 delocate: Use adrp/add in loadAarch64Address by David Benjamin · 6 days ago
  3. ec8ba76 Compute the FIPS module hash after evaluating relocations by David Benjamin · 6 days ago
  4. b74ac2b inject_hash: Support finding the marker symbols in .symtab or .dynsym by David Benjamin · 5 days ago
  5. fcc7c83 Test clearing out-of-bounds bits with ASN1_BIT_STRING_set_bit by David Benjamin · 4 days ago

BoringSSL

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:

To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.

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