Google Git
Sign in
boringssl / boringssl / 0f55aa8416787562e57bc962b9c4aeb70261cb7c
commit0f55aa8416787562e57bc962b9c4aeb70261cb7c[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Oct 08 22:09:51 2024 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Oct 10 13:11:06 2024 +0000
treeb78fe1749ba7b869a50e1f13d2879647c6a4f27e
parent905c3903fd4291a22328346861ddf15599a7c33b [diff]
Use InplaceVector for the various handshake derivations

While I'm here, remove a TODO about DTLS 1.3. DTLS 1.3 has opted to
switch to the TLS 1.3 transcript format, instead of the weird DTLS 1.2
one, so that code should work just fine.

This does mean we store each field's length separately. On the flip
side, the lengths are now single bytes and the old shared length was was
a size_t. Either way, the SSL_HANDSHAKE structure is released after the
handshake, so memory usage is less of a premium.

Change-Id: I43530d57b11f78852be478b9051d30a4657cdc4c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71967
Reviewed-by: Adam Langley <agl@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
8 files changed
tree: b78fe1749ba7b869a50e1f13d2879647c6a4f27e
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. pki/
  11. rust/
  12. ssl/
  13. third_party/
  14. tool/
  15. util/
  16. .bazelignore
  17. .bazelrc
  18. .clang-format
  19. .gitignore
  20. API-CONVENTIONS.md
  21. BREAKING-CHANGES.md
  22. BUILD.bazel
  23. build.json
  24. BUILDING.md
  25. CMakeLists.txt
  26. codereview.settings
  27. CONTRIBUTING.md
  28. FUZZING.md
  29. go.mod
  30. go.sum
  31. INCORPORATING.md
  32. LICENSE
  33. MODULE.bazel
  34. MODULE.bazel.lock
  35. PORTING.md
  36. PrivacyInfo.xcprivacy
  37. README.md
  38. SANDBOXING.md
  39. STYLE.md
README.md

BoringSSL

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: