Clone this repo:
  1. a12a249 Const-correct various X509_NAME APIs. by David Benjamin · 2 weeks ago master
  2. 7940ed1 Ignore old -enable-ed25519 flag. by Adam Langley · 3 days ago
  3. f1efbc8 Provide __NR_getrandom fillins in urandom test too. by Adam Langley · 3 days ago
  4. aadb463 Skip RSATest.DISABLED_BlindingCacheConcurrency in SDE. by David Benjamin · 5 weeks ago
  5. 754d4c9 Fix client handling of 0-RTT rejects with cipher mismatch. by David Benjamin · 6 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: