Clone this repo:


  1. 0768d42 include needed headers by Adam Langley · 20 hours ago main
  2. f1d153d Don't overread in poly_Rq_mul by Adam Langley · 20 hours ago
  3. 5799ebf acvp: recognise another style of JSON. by Adam Langley · 5 days ago
  4. d422d2c Revert "Revert "Revert "Disable check that X.509 extensions implies v3.""" by David Benjamin · 7 days ago
  5. c1571fe acvp: add HKDF support. by Adam Langley · 11 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.

Project links:

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