Clone this repo:
  1. 46a1c7e Add EVP_HPKE_KEM_public_key_len and EVP_HPKE_KEM_private_key_len. by David Benjamin · 2 days ago master
  2. 80eb814 Remove the experimental in-place record APIs. by David Benjamin · 8 days ago
  3. 32013e8 Maintain the sequence number as a uint64_t. by David Benjamin · 9 days ago
  4. cab31f6 Add int64 ASN1_INTEGER setters too. by David Benjamin · 8 days ago
  5. a61e747 Also check for V_ASN1_NEG_INTEGER when checking types. by David Benjamin · 8 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: