Clone this repo:
  1. 47c0f1f CI/CQ: in debug builds, enable lots of libc++ checks. by Rudolf Polzer · 2 hours ago upstream/main
  2. 7fef640 Minor optimizations to ML-DSA: marking some internal functions inline. by Rudolf Polzer · 5 hours ago
  3. b008298 Switch STACK_OF(T) back to std::sort from std::stable_sort by David Benjamin · 19 hours ago
  4. db1bdbc Use the certificate issuer in CMS/PKCS7 signer IDs by David Benjamin · 21 hours ago
  5. bb47b7e rust: bssl-macros: Do not depend on std by Xiangfei Ding · 21 hours 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: