Clone this repo:
  1. 441efad Add RSA_PSS_PARAMS to bssl::UniquePtr. by David Benjamin · 36 hours ago master
  2. e759a9c Support the OpenSSL “pass zero for strlen” when setting X.509 hostnames. by Adam Langley · 22 hours ago
  3. d67e311 Test BN_primality test with OEIS A014233 values . by David Benjamin · 3 days ago
  4. 88e6a05 Configure asmjs and wasm as generic, 32-bit machines. by Adam Langley · 3 days ago
  5. d61334d Document preferences for EC_GROUP_new_by_curve_name. by David Benjamin · 3 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: