Clone this repo:
  1. d977eaa Make AES-GCM AEADs support the optional second input argument to seal_scatter. by Martin Kreichgauer · 2 days ago master
  2. 74bce29 Change EVP_AEAD_CTX_seal_scatter to support an additional plaintext input. by Martin Kreichgauer · 4 days ago
  3. 946dd62 AES-GCM shouldn't keep its own version of the tag length. by Adam Langley · 6 hours ago
  4. 3120950 Size TLS read buffers based on the size requested. by David Benjamin · 5 days ago
  5. 5df5be1 Fix record header callback on writes. by David Benjamin · 5 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.

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