Clone this repo:
  1. a0ba400 Add cipher asserts for read/write app data. by Steven Valdez · 3 hours ago master
  2. ccbb165 Tidy up ssl3_choose_cipher. by David Benjamin · 6 days ago
  3. 8c26d75 Test the behavior of running SSL_do_handshake twice in a row. by David Benjamin · 2 days ago
  4. 7a60ca0 Synchronize with upstream. by David Benjamin · 2 days ago
  5. 0f5d7d3 Just allocate what's needed for SSL write buffers. by David Benjamin · 32 hours 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: