commit | 12a48b2b110a2f3ed705fa4660e82831c5709cdb | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Oct 08 12:38:02 2024 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 08 21:40:10 2024 +0000 |
tree | f788b6780e96548757874dbe0ee74d5a2fa066f8 | |
parent | 8116e734958854614d0e87b2b6a1efb7d9231960 [diff] |
Make bssl::Vector not require a default constructor Rather than leaving default-initialized things in there, a real std::vector implementation leaves the elements passed size_ unconstructed and constructs them as needed. Change-Id: Ib884e2c10894de011d75a46037b446088195ba96 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71828 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: