Clone this repo:
  1. afdbb62 Ensure that BIO_[w]pending isn't confused about negative numbers. by Adam Langley · 22 hours ago master
  2. fc4467e Refresh fuzzer corpus. by David Benjamin · 2 days ago
  3. 7784c4c Fix fuzzer mode suppressions. by David Benjamin · 2 days ago
  4. 9559401 Use SHA256_CTX instead of EVP_MD_CTX when computing Channel ID. by Nick Harper · 2 days ago
  5. c984611 Fix bogo implementation of Channel ID for TLS < 1.2. by Nick Harper · 5 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: