diff --git a/quest/a1/rind/README.md b/quest/a1/rind/README.md index 79d4f031..3cc914d9 100644 --- a/quest/a1/rind/README.md +++ b/quest/a1/rind/README.md @@ -2,9 +2,9 @@ ## Goal -Every Rust crate here except Quiche takes its TLS crypto only from [rind](https://github.com/moq-dev/rind) through `rind-rustls`, so no build compiles C crypto. On every release target, `cargo tree -e normal,build -i` finds no aws-lc-sys, ring, or `cc` reached through a crypto crate. The crates' `aws-lc-rs` and `ring` features are removed. +Every Rust crate here except Quiche and QMux takes its TLS crypto only from [rind](https://github.com/moq-dev/rind) through `rind-rustls`, so their builds compile no C crypto. For those crates on every release target, `cargo tree -e normal,build -i` finds no aws-lc-sys, ring, or `cc` reached through a crypto crate. Their `aws-lc-rs` and `ring` features are removed. -Non-goals: web-transport-quiche, which is BoringSSL (rind doesn't apply), and WASM, which uses the browser's TLS. +Non-goals: web-transport-quiche, which is BoringSSL (rind doesn't apply); qmux, which is being retired in favour of [moq-dev/moq's qmux](https://github.com/moq-dev/moq/blob/main/rs/qmux/MIGRATE.md), already on rind; and WASM, which uses the browser's TLS. ## Plan @@ -18,8 +18,8 @@ Decided with the maintainer on 2026-11-06 (planning interview, following moq's [ The epic's own work, once every child has merged: -- A CI guard that no release target's normal or build graph holds aws-lc-sys, ring, or `cc` through a crypto crate. Quiche's graph is exempt. -- Remove leftover aws-lc-rs and ring from the workspace, except dev-dependencies that only tests use. +- A CI guard that no release target's normal or build graph holds aws-lc-sys, ring, or `cc` through a crypto crate. Quiche's and QMux's graphs are exempt. +- Remove leftover aws-lc-rs and ring from the workspace, except QMux's and dev-dependencies that only tests use. Decision prompts (✅ chosen): @@ -36,4 +36,3 @@ Decision prompts (✅ chosen): - [Quinn on rind](/quest/a1/rind/quinn.md) - provider-neutral QUIC crypto adapter; Quinn, FFI, Node and router on rind - [Noq on rind](/quest/a1/rind/noq.md) - Noq's rustls without ring, with rind keys - [iroh on rind](/quest/a1/rind/iroh.md) - iroh endpoint built with rind's provider -- [QMux on rind](/quest/a1/rind/qmux.md) - TLS and WSS paths with no aws-lc-rs diff --git a/quest/a1/rind/qmux.md b/quest/a1/rind/qmux.md deleted file mode 100644 index fc4c8737..00000000 --- a/quest/a1/rind/qmux.md +++ /dev/null @@ -1,11 +0,0 @@ -# [S] Run QMux's TLS and WSS paths on rind - -## Goal - -qmux's `tls` and `wss` features compile no aws-lc-rs or ring. A connection the caller doesn't configure runs on rind-rustls, and one the caller configures keeps their `rustls` config. - -## Plan - -Today aws-lc-rs comes in through qmux's own `rustls` and `tokio-rustls` dependencies (both with default features) and through `tokio-tungstenite/rustls-tls-native-roots`, which enables rustls's default provider. Depend on rustls and tokio-rustls with `default-features = false`, and pick tokio-tungstenite features that bring no provider. Where qmux or tungstenite would build a default `ClientConfig` (a WSS connect with no connector), build it on the installed process provider, else rind, with native roots. A CPU rind refuses returns an error. - -Check every qmux feature combination with `cargo tree -e normal,build -i aws-lc-sys` and `-i ring`. `tls::Client`/`tls::Server` always take a caller config, so they get no default. Test a TLS handshake with a caller config built on rind, and a WSS handshake with no caller config. Whether to also change the `qmux-v0.5.x` line is a separate decision, not part of this quest.