| commit | 5813c2c10c73d800f1b0d890a7d74ff973abbffc | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Wed Oct 30 14:48:00 2024 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 26 21:10:44 2024 +0000 |
| tree | 0f6d13a15857fe96f2dac5e58dee9ffe0945f9f4 | |
| parent | 7a6022067f5cd740c8bf9b067eab9012797b654c [diff] |
crypto: switch to C++ This change switches nearly all of BoringSSL to use C++. The public functions still use the C ABI, and so code written in C can still use BoringSSL. Also the use of the C++ standard library is minimal and no run-time requirement for it is intended. Change-Id: I902d2f51a3c8d6bd0dc4aabe1b192a15d7b788e8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72747 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Bob Beck <bbe@google.com>
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: