Mirror of BoringSSL (grpc依赖)
https://boringssl.googlesource.com/boringssl
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tag:
Branch:
Tree:
16c42cc796
2214
2272
2311
2357
2490
2564
2623
2661
2704
2785
2883
2924
2987
3029
3071
3112
3202
3239
3282
3359
3538
3945
chromium-2214
chromium-2272
chromium-2311
chromium-2357
chromium-2490
chromium-2564
chromium-2623
chromium-2661
chromium-2704
chromium-2883
chromium-2924
chromium-2987
chromium-3029
chromium-3071
chromium-3112
chromium-3202
chromium-3239
chromium-3282
chromium-3359
chromium-3538
chromium-3945
chromium-5359
chromium-5414
chromium-stable
chromium-stable-with-bazel
esni
fips-20180730
fips-20220613
fips-20230428
fips-20240407
fips-20240805
fips-20250107
fips-android-20191008
grpc-202302
infra/config
main
main-with-bazel
master
master-with-bazel
0.20240913.0
0.20240930.0
0.20241024.0
0.20241203.0
0.20241209.0
0.20250114.0
0.20250212.0
fips-20170615
fips-20180730
fips-20190808
fips-20210429
fips-20220613
fips-android-20191020
version_for_cocoapods_1.0
version_for_cocoapods_10.0
version_for_cocoapods_2.0
version_for_cocoapods_3.0
version_for_cocoapods_4.0
version_for_cocoapods_5.0
version_for_cocoapods_6.0
version_for_cocoapods_7.0
version_for_cocoapods_8.0
version_for_cocoapods_9.0
${ noResults }
boringssl/include
QUICHE currently does not know to call SSL_set_quic_use_legacy_codepoint, picking up the current default of the legacy code point. It then assumes that the TLSEXT_TYPE_quic_transport_parameters constant may be used to extract transport parameters, so after https://boringssl-review.googlesource.com/c/boringssl/+/44704, it breaks. To smooth over the transition, we now define three constants: TLSEXT_TYPE_quic_transport_parameters_legacy, TLSEXT_TYPE_quic_transport_parameters_standard, and the old constant. The old constant will match whatever the default is (for now, legacy) so the default is self-consistent. Then plan is then: 1. BoringSSL switches to the state in this CL: the default code point and constant are the legacy one, but there are APIs to specify the code point. This will not affect QUICHE, which only uses the defaults. 2. QUICHE calls SSL_set_quic_use_legacy_codepoint and uses the corresponding _legacy or _standard constant. It should *not* use the unsuffixed constant at this point. 3. BoringSSL switches the default setting and the constant to the standard code point. This will not affect QUICHE, which explicitly configures the code point it wants. 4. Optional: BoringSSL won't switch the default back to legacy, so QUICHE can switch _standard to unsuffixed and BoringSSL can remove the _standard alias (but not the function) early. 5. When QUICHE no longer needs both code points, it unwinds the SSL_set_quic_use_legacy_codepoint code and switches back to the unsuffixed constant. 6. BoringSSL removes all this scaffolding now that it's no longer needed. Update-Note: This this fixes a compatibility issue with https://boringssl-review.googlesource.com/c/boringssl/+/44704. Change-Id: I9f75845aba58ba93e9665cd6f05bcd080eb5f139 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45124 Reviewed-by: David Schinazi <dschinazi@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> |
4 years ago | |
---|---|---|
.. | ||
openssl | Define TLSEXT_TYPE_quic_transport_parameters to the old code point for now. | 4 years ago |