| commit | 3d8b8c3df27cc780a49607be6a27f2c518f5c082 | [log] [tgz] |
|---|---|---|
| author | David Schinazi <dschinazi@google.com> | Thu Jan 14 11:25:49 2021 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 14 21:22:33 2021 +0000 |
| tree | aff7e8b69177ef028ed0b93ec0f79cd1e6d127d7 | |
| parent | f8f35c95550e6796ab8b2c0f8e37e7ce4bc67302 [diff] |
Add support for the new QUIC TLS extension codepoint IETF QUIC draft 33 is replacing the TLS extension codepoint for QUIC transport parameters from 0xffa5 to 57. To support multiple versions of Chrome, we need to support both codepoints in BoringSSL. This CL adds support for the new codepoint in a way that can be enabled on individual connections. Note that when BoringSSL is not in QUIC mode, it will error if it sees the new codepoint as a server but it will ignore the legacy codepoint as that could be a different private usage of that codepoint. Change-Id: I314f8f0b169cedd96eeccc42b44153e97044388c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/44704 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: 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:
There are other files in this directory which might be helpful: