Bump quic to 1.6.2#864
Merged
Merged
Conversation
Brings cross-signed expired-root recovery to the QUIC TLS stack, so HTTP/3 and WebTransport-over-HTTP/3 handle an expired cross-signed root (e.g. Let's Encrypt ISRG Root X2 cross-signed by the expired X1), matching the fix already in place for HTTP/1.1 and HTTP/2.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bump the quic dependency to 1.6.2.
1.6.2 adds cross-signed expired-root recovery to the QUIC TLS validation (
quic_cert): an expired cross-signed root is dropped for a still-valid anchor with the same key, while an expired leaf or intermediate still fails. This gives HTTP/3 and WebTransport-over-HTTP/3 the same behaviour we already have for HTTP/1.1 and HTTP/2 (#863). No hackney code change needed.