Clone this repo:
  1. 3ab3b12 Add compatibility functions for sigalgs by Shelley Vohr · 2 days ago master
  2. de1d288 Run AES-192-GCM in CAVP tests. by Adam Langley · 33 hours ago
  3. 3ba9586 Rename a number of BUF_* functions to OPENSSL_*. by David Benjamin · 34 hours ago
  4. 31f94b0 List bn_div fuzzer in documentation. by Adam Langley · 2 days ago
  5. c951e55 Reenable bn_div fuzzer. by David Van Cleve · 2 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: