| commit | 2c801827ec88088a83d5c9572b29604b0a4577e6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 22 16:01:42 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 25 18:35:00 2024 +0000 |
| tree | 1856076aceb2a1e05ef57316dc8729bf4651baf9 | |
| parent | 9588d3c35d43f3bb27f4fa8dff8e65bf6b84d2a5 [diff] |
Store an Array in hm_fragment Also rename it to DTLSIncomingMessage to mirror DTLSOutgoingMessage. (Also renamed to be C++ style like other, slightly more C++-y, internals.) It is slightly less compact in memory to store the size as a size_t rather than a uint32_t that can be packed in there, but this object is largely discarded after the handshake, and this way we get more bounds checking. I haven't actually replaced the memcpy with a span-based copy since we don't have one yet, but this opens the door for that. Bug: 374890768 Change-Id: I0f69fc4ca64bebed95d90979ec99fe1ea57c66fb Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72273 Reviewed-by: Nick Harper <nharper@chromium.org> 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: