Clone this repo:
  1. 2fcdd11 Make BoringSSL initialization-less by David Benjamin · 3 days ago master
  2. 6c98ebe Call CRYPTO_library_init before ChaCha20 and P-256 assembly by David Benjamin · 6 days ago
  3. d1e6d3b test_fips: two tweaks by Adam Langley · 2 days ago
  4. 84dc9bb Add EDDSA support for fetching and uploading vectors by Sven Biebaut · 2 days ago
  5. 67422ed test_fips: don't forget a couple of \n's by Adam Langley · 3 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: