Repository navigation
Release 4.11.1 - #1029
Merged
Merged
Release 4.11.1#1029
Conversation
Security release: an unusable cacertfile no longer falls back to the system trust store, and per-session memory is now bounded.
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
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.
Security release bumping webtransport to 0.5.8.
Before, a WebTransport
cacertfilethat could not be read was skipped and, over HTTP/3, the server was checked against the system trust store instead of the CAs you chose. A server could also make a WebTransport session grow its memory without limit. Both are fixed in webtransport 0.5.7/0.5.8.Behavior change: a WebTransport send that would exceed 4 MiB waiting for flow-control credit now returns
{error, send_buffer_full}.