Clone this repo:
  1. df08c3a perlasm scripts: work better if the command interpreter is cmd.exe. by Rudolf Polzer · 2 days ago main
  2. 44a1a1f Pregenerate: emit all assembly function names by Xiangfei Ding · 5 days ago
  3. c2d2325 extract_identifiers_clang_json: factor out Clang AST logic. by Rudolf Polzer · 6 days ago
  4. 6fe076b Namespace crypto/fipsmodule/sha's internal symbols. by Rudolf Polzer · 10 days ago
  5. 7a9a8e2 Remove paths.cmake as it is no longer in use. by Rudolf Polzer · 5 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:

To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.

There are other files in this directory which might be helpful: