Clone this repo:
  1. 059585c Update tools and add a .bazelversion by David Benjamin · 7 days ago master
  2. fcef13a Speed up sha512 on x86 by Ilya Tokar · 6 days ago
  3. 5813c2c crypto: switch to C++ by Adam Langley · 5 weeks ago
  4. 7a60220 Remove the old SSL_R_APPLICATION_DATA_INSTEAD_OF_HANDSHAKE logic by David Benjamin · 6 days ago
  5. 9a85565 Don't access the read_buffer directly in read_v2_client_hello by David Benjamin · 6 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: