| commit | d0a175601b9e180ce58cb1e33649057f5c484146 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 08 17:20:13 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 08 22:33:27 2024 +0000 |
| tree | 9f7605f616431374a07811fcf56b59e2406fc229 | |
| parent | 87d0c174c7fdc4c48b74b60e8f2f44852f41c6bf [diff] |
Switch outgoing_messages to InplaceVector This required adding a PushBack method. I removed the check for 32-bit size_t. That dates to https://boringssl-review.googlesource.com/20671 when the input object had a 64-bit size_t, but we only stored a uint32_t size in memory. We now just store an Array without any fuss (the abstraction was worth more than the memory packing), so this is all moot. (It will also never get that large because CBB will refuse to construct it.) Change-Id: Idf4ad7e47a81b8086ef0fed2083308aaf0efb668 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71848 Reviewed-by: Adam Langley <agl@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: