fix(deps): update module github.com/quic-go/quic-go to v0.50.0 #196
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.
This PR contains the following updates:
v0.49.0
->v0.50.0
Release Notes
quic-go/quic-go (github.com/quic-go/quic-go)
v0.50.0
Compare Source
This release implements server-side path-probing (as described in section 9 of RFC 9000): #4932, #4933, #4935, #4938, #4939, #4940, #4941, #4944, #4947, #4959.
When the server receives a packet for an existing connection from a different IP address / port, it first needs to probe the new path before it can send packets on that path. This happens when the client experiences a NAT rebinding, and when the client attempts to migrate to a new connection. Previous versions of quic-go would accept the packets from the new path, but never switch to the new path.
Note that the client side connection migration logic (#234) is not yet implemented in quic-go (but we're working on it!).
Major Changes
Other Fixes
Go 1.24 FIPS 140-3 Caveats
Go 1.24 made several changes related to FIPS 140-3 compliance. Among others, it introduced a
fips-only
mode (enabled by settingGODEBUG="fips140=only"
).It is not possible to use quic-go in fips-only mode, since the QUIC RFC requires initializing an AES GCM cipher with a fixed nonce, which is considered unsafe according to FIPS 140-3, or at least the Go team's interpretation thereof. See https://github.com/quic-go/quic-go/issues/4894 and the discussion on Go issue #69536.
Before v0.50.0, quic-go would initialize the AES cipher on
init
, leading to a panic when using fips-only mode. For v0.50.0 we changed this behavior to lazy initialization (https://github.com/quic-go/quic-go/pull/4916). Note that this still means it's not possible to use QUIC in fips-only mode.Changelog
Full Changelog: quic-go/quic-go@v0.49.0...v0.50.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.