| commit | a66e808c0f15a42b6e9b5b5c42cc02d458835da1 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Tue Jan 07 10:31:33 2025 -0800 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 07 10:47:27 2025 -0800 |
| tree | 6d41651bf45efc8c79d4e486e84b478463419aa4 | |
| parent | 0093ff3137d0f2bc6bbd5fdafea6929f1b107bd3 [diff] |
Revert "Always try and enable the new_uninit feature." This reverts commit d678fbfb4802deac0258a9a53eac960d6e6e1bc5. The original change broke Chromium: ``` error[E0725]: the feature `new_uninit` is not in the list of allowed features --> ../../third_party/boringssl/src/rust/bssl-crypto/src/lib.rs:28:12 | 28 | #![feature(new_uninit)] | ^^^^^^^^^^ ``` Change-Id: I6732a720a5705cfe7b0219b5d9d02a911af0f89a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/74987 Auto-Submit: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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: