Clone this repo:
  1. 88024df Remove -enable-ed25519 compat hack. by Adam Langley · 3 days ago master
  2. 53a17f5 Add a |SSL_process_tls13_new_session_ticket|. by Adam Langley · 10 days ago
  3. 2309f64 Use ctr32 optimizations for AES_ctr128_encrypt. by David Benjamin · 2 weeks ago
  4. 8819e0b Test AES mode wrappers. by David Benjamin · 2 weeks ago
  5. 81a998a Bump minimum CMake version. by David Benjamin · 10 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: