1a444daca6
This is kind of annoying (even new state is needed to keep the layering right). As part of aligning the read paths of the TLS 1.2 and TLS 1.3 state machine, we'll want to move to states calling ssl_hash_current_message when the process the message, rather than when the message is read. Right now the TLS 1.2 optional message story (reuse_message) depends on all messages preceded by an optional message using ssl_hash_message. For instance, if TLS 1.2 decided to place CertificateStatus before ServerKeyExchange, we would not be able to handle it. However, V2ClientHello, by being handled in the message layer, relies on ssl_get_message-driven hashing to replace the usual ClientHello hash with a hash of something custom. This switches things so rather than ClientHellos being always pre-hashed by the message layer, simulated ClientHellos no-op ssl_hash_current_message. This just replaces one hack with another (V2ClientHello is inherently nasty), but this hack should be more compatible with future plans. BUG=128 Change-Id: If807ea749d91e306a37bb2362ecc69b84bf224c9 Reviewed-on: https://boringssl-review.googlesource.com/13265 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
|---|---|---|
| .github | ||
| crypto | ||
| decrepit | ||
| fuzz | ||
| include/openssl | ||
| infra/config | ||
| ssl | ||
| third_party | ||
| tool | ||
| util | ||
| .clang-format | ||
| .gitignore | ||
| API-CONVENTIONS.md | ||
| BUILDING.md | ||
| CMakeLists.txt | ||
| codereview.settings | ||
| CONTRIBUTING.md | ||
| FUZZING.md | ||
| INCORPORATING.md | ||
| LICENSE | ||
| PORTING.md | ||
| README.md | ||
| STYLE.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.
There are other files in this directory which might be helpful:
- PORTING.md: how to port OpenSSL-using code to BoringSSL.
- BUILDING.md: how to build BoringSSL
- INCORPORATING.md: how to incorporate BoringSSL into a project.
- API-CONVENTIONS.md: general API conventions for BoringSSL consumers and developers.
- STYLE.md: rules and guidelines for coding style.
- include/openssl: public headers with API documentation in comments. Also available online.
- FUZZING.md: information about fuzzing BoringSSL.
- CONTRIBUTING.md: how to contribute to BoringSSL.