Clone this repo:
  1. 6ce77af Unexport X509V3_NAME_from_section and fix the type of chtype. by David Benjamin · 2 weeks ago master
  2. faac9aa Finish porting dh_test.cc and ripemd_test.cc to GTest. by David Benjamin · 6 days ago
  3. 1e63b0c Replace comment with static assert. by David Benjamin · 6 days ago
  4. b15e56a Add a tool to check whether a binary has an executable stack by David Benjamin · 23 hours ago
  5. 785bb12 Disable blinding for boringssl_self_test_rsa(). by hehe.li · 3 days ago

BoringSSL

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: