Clone this repo:
  1. 1c6e104 Disable fork detection for Zephyr and CrOS EC by Patryk Duda · 18 hours ago master
  2. bdb7b19 Enable thread support for Zephyr RTOS by Patryk Duda · 8 days ago
  3. 6b3e5d5 Fix Zephyr define and description by Patryk Duda · 8 days ago
  4. 4898d3f Remove unnecessary NULL checks by Theo Buehler · 3 weeks ago
  5. 89f0977 Avoid strdup in crypto/err/err.c by David Benjamin · 5 months 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: