Clone this repo:
  1. 8dcdcb3 acvp: drop 3DES fields from output when unused. by Adam Langley · 25 hours ago master
  2. 0f0e2bc acvp: don't advertise SHA-1 RSA signature generation. by Adam Langley · 25 hours ago
  3. 39093c1 Fix comments that refer to old draft of HPKE. by Dan McArdle · 30 hours ago
  4. c47bfce Define TLSEXT_TYPE_quic_transport_parameters to the old code point for now. by David Benjamin · 2 days ago
  5. 2d691ca Make BN_clear_free a wrapper around BN_free. 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: