83a321231b
Recent changes added SSL-level setters to these APIs. Unfortunately, this has the side effect of breaking SSL_set_SSL_CTX, which is how SNI is typically handled. SSL_set_SSL_CTX is kind of a weird function in that it's very sensitive to which of the hodge-podge of config styles is in use. I previously listed out all the config styles here, but it was long and unhelpful. (I counted up to 7.) Of the various SSL_set_SSL_CTX-visible config styles, the sanest seems to be to move it to CERT. In this case, it's actually quite reasonable since they're very certificate-related. Later we may wish to think about whether we can cut down all 7 kinds of config styles because this is kinda nuts. I'm wondering we should do CERT => SSL_CONFIG, move everything there, and make that be the same structure that is dropped post-handshake (supposing the caller has disavowed SSL_clear and renego). Fruit for later thought. (Note though that comes with a behavior change for all the existing config.) Change-Id: I9aa47d8bd37bf2847869e0b577739d4d579ee4ae Reviewed-on: https://boringssl-review.googlesource.com/13864 Reviewed-by: Martin Kreichgauer <martinkr@google.com> 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.