Clone this repo:
  1. be2ee34 Update AES-GCM-SIV to match revision four of the draft. by Adam Langley · 3 days ago master
  2. 5ae4165 Allow multiple IDN xn-- indicators by Alessandro Ghedini · 4 days ago
  3. adec772 Remove SSL_CIPHER_has_MD5_HMAC. by David Benjamin · 8 days ago
  4. de5c325 Fix SSL_write doc comment by Michel Lespinasse · 5 days ago
  5. a57dcfb Add new cipherlist-setting APIs that reject nonsense. by Matthew Braithwaite · 9 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: