Clone this repo:
  1. bd20800 Add a comment for what is about by David Benjamin · 2 days ago master
  2. d24a382 Sync pki to chromium eddbcb143c7462e0b8d60e859b96d678ca0c013c by Bob Beck · 5 days ago
  3. 764e6a3 Stop rewriting ret to repz ret on x86_64 by David Benjamin · 5 days ago
  4. cfcb954 Make bssl-crypto no_std compatible by Alice Wang · 10 days ago
  5. a1843d6 Bump the minimum CMake version to 3.12 by David Benjamin · 2 weeks 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: