Clone this repo:
  1. 21558f4 Document error behavior of PKCS5_PBKDF2_HMAC and EVP_PBE_scrypt by Joshua Liebow-Feeser · 6 days ago master
  2. 1c2779e Don't let a NULL mean the initial SSL_CTX in SSL_set_SSL_CTX. by Adam Langley · 4 days ago
  3. 929fd44 Update URL for GN quick start guide. by Tom Bridgwater · 4 days ago
  4. a130ce0 Update TLS 1.3 citations for the final RFC. by David Benjamin · 6 days ago
  5. c4131a4 Support the allocating case of i2d_ASN1_{BOOLEAN,OBJECT}. 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.

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