diff --git a/quest/m0/release-backports/README.md b/quest/m0/release-backports/README.md index d2f54d4c891..723070da2d1 100644 --- a/quest/m0/release-backports/README.md +++ b/quest/m0/release-backports/README.md @@ -47,7 +47,6 @@ findings; expanding this shortlist needs a separate scope decision. ## Required -- [TLS dependencies](/quest/m0/release-backports/tls.md) - release takes the targeted WebPKI fixes already on main - [JS input parsing](/quest/m0/release-backports/parsing.md) - malformed certificates and paths cannot trigger disproportionate parsing work - [FFI cancellation](/quest/m0/release-backports/ffi-cancellation.md) - cancelled reads and accepts leave the next event for the next caller diff --git a/quest/m0/release-backports/tls.md b/quest/m0/release-backports/tls.md deleted file mode 100644 index 6da7401aae8..00000000000 --- a/quest/m0/release-backports/tls.md +++ /dev/null @@ -1,22 +0,0 @@ -# [XS] Backport the WebPKI dependency fixes - -## Goal - -Release's TLS consumers use the WebPKI fixes already on main without -unrelated dependency upgrades or changes to the published API or wire. - -## Plan - -Decided 2026-10-22 (maintainer): include this in the focused patch backports. -At release 36f392f492, Cargo.lock has rustls-webpki 0.103.15 and -webpki-root-certs/webpki-roots 1.0.9. Main took 0.103.16 and 1.0.10 in -[moq-dev/moq#6169](https://github.com/moq-dev/moq/pull/6169). -The later [moq-dev/moq#6197](https://github.com/moq-dev/moq/pull/6197) names -the security updates but its actual patch only changes a getrandom edge. - -Verify the upstream advisory fixes and update the affected locked packages -on release. Do not cherry-pick the broad dependency-audit patch, which also -upgrades GStreamer. Check the resulting dependency graph, advisory audit, -and affected TLS builds through the release gate. The consumers are existing -native clients and relays that validate peer certificates. No package version -bump, public API change, or MoQ wire change belongs in this backport.