| commit | 943987096f1a20d3e21a9b115b851d048b19ac7c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Feb 11 13:47:02 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 11 13:24:53 2025 -0800 |
| tree | 6ab88c05fb8f1ee7f91af101f00593516bb54dab | |
| parent | ce25d4b750e2ca0b68b8731aa2b4ce61d014a790 [diff] |
Add SSL_parse_client_hello Applications sometimes need to create SSL_CLIENT_HELLO objects for testing. We already have this function internally. Just expose it as public API. The only non-trivial change here is I've moved the error queue bits from the caller of ssl_client_hello_init to inside SSL_parse_client_hello. This matches our conventions a bit better (usually functions are responsible for originating the error), and keeps ssl.h's public APIs consistently using the error queue here. Bug: 395069491 Change-Id: I16fb35772a61e98d2621f781e475aa5611b13582 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76128 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: 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: