| commit | b5879118ac2067f036f55497eba034940fbb791c | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue May 18 17:10:18 2021 -0400 |
| committer | Adam Langley <agl@google.com> | Thu Jun 03 20:54:12 2021 +0000 |
| tree | 0b22d3ef21f4f25f060b4743036a0680e626525c | |
| parent | 8acec00e9eaf4d69297a67c0c10729470b4bd764 [diff] |
Remove the Channel ID callback. The remaining remnants of Channel ID all configure the private key ahead of time. Unwind the callback machinery, which cuts down on async points and the cases we need to test. This also unwinds some odd interaction between the callback and SSL_set_tls_channel_id_enabled: If a client uses SSL_set_tls_channel_id_enabled but doesn't set a callback, the handshake would still pause at SSL_ERROR_WANT_CHANNEL_ID_LOOKUP. This is now removed, so SSL_set_tls_channel_id_enabled only affects the server and SSL_CTX_set1_tls_channel_id only affects the client. Update-Note: SSL_CTX_set_channel_id_cb is removed. SSL_set_tls_channel_id_enabled no longer enables Channel ID as a client, only as a server. Change-Id: I89ded99ca65e1c61b1bc4e009ca0bdca0b807359 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/47907 Reviewed-by: Adam Langley <agl@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:
There are other files in this directory which might be helpful: