Repository navigation
Conversation
Quest-Claim: 0c1f0d889661366b
Use rind TLS, initial protection and endpoint keys with fallible CPU checks. Preserve the quest and draft until rind-rustls publishes path-aware packet methods required by Noq. Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
This was referenced Nov 7, 2026
This branch has not been deployed
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.
Noq's rind migration is checkpointed here and remains a draft because the published provider cannot encrypt Noq packets. No package version or release changes are included.
Waiting
PacketKey::encrypt_in_place_for_pathanddecrypt_in_place_for_path, including path 0, inrind-rustls, and publish a stable version containing them. Update this PR's dependency to that stable release; verifyrind_packet_keys_support_noq_path_apiandring_peer_handshake_and_retrypass, then complete the full repository checks and committed-head cross-vendor review before marking ready. Publishedrind-rustls0.23.0 and rind main6dbdebd578aa2c36b7109261009084148a183aadlack both methods.Changes and choices
UnsupportedCpufrom finishing methods.Client::default()documents its unwrap.with_initialconstructors. Use rind HMAC-SHA256 reset keys and Noq-compatible HKDF-SHA256/AES-256-GCM Retry/validation-token keys, with helpers for fresh keys and types for persistent secrets.Compatibility
Breaking Rust API change: remove
aws-lc-rsandringCargo features;crypto::default_provider()andcrypto::sha256()returnResult; client/server errors gain CPU, crypto and client I/O variants. Advanced callers keep Noq's rustls types andHandshakeData, but usewith_initialand explicit endpoint/server keys. The README and advanced examples show the migration. No intended QUIC or HTTP/3 wire change. The current draft is not runnable until the upstream blocker clears.Blocker evidence
Noq invokes the path-aware packet method for every packet, including initial path 0, and unwraps encryption in noq-proto 1.4's adapter. Rustls's default path-aware methods return
EncryptError/DecryptError. Rind's current packet implementation implements only the non-path methods. This failure is caused by switching Noq to the incomplete provider, not a pre-existing base failure.Validation
All builds/tests use the Nix shell and the installed
quest gate; no validation harness was changed.just fix: passed, including native/WASM cargo fix and Clippy, formatting, dependency checks and JS fixes. No incidental source changes remained.cargo check -p web-transport-noq --all-targets --all-features: passed.cargo build -p web-transport-noq --lib --no-default-features: passed.installed_provider_and_cpu_refusal,reset_hmac_matches_ring_and_rejects_invalid_signaturesandtoken_encryption_matches_noq_ring_construction_and_authenticates: passed. The provider test isolates process-global installation and tests CPU refusal at every finishing method.cargo tree -p web-transport-noq -e normal,build --target <target>: no ring, aws-lc-rs, aws-lc-sys orccacross 15 targets covering Linux GNU/musl, Windows MSVC, macOS, iOS and Android on x86_64/aarch64/armv7. These are dependency-resolution checks, not cross-compilation claims.cargo test -p web-transport-noq --test crypto rind_packet_keys_support_noq_path_api -- --exact: failed immediately at path 0:Noq requires path-aware packet encryption: EncryptError(the focused test is committed atrs/web-transport-noq/tests/crypto.rs:242). This is the dependency blocker, not a passing/ignored test.cargo test -p web-transport-noq --test crypto --all-features: the deterministic HMAC/token tests pass, butring_peer_handshake_and_retryaborts atnoq-proto-1.4.0/src/crypto/rustls.rs:649:called Result::unwrap() on an Err value: EncryptError. The full Noq all-target/all-feature test command aborts at the same point in the migrated session fixture. The complete workspacejust testwas not run after this reproduced blocker.nix develop --command <installed-quest> gate just check: failed before compilation because its pinnedquest checkrejects## Waitingas an unknown heading. The requested installed Quest'squest check --base origin/mainpasses, including this accurate outside-condition entry. No flake pin or repository harness was changed to bypass the old validator.git diff --check: passed.Checkpoint:
ab42f74fd13b15b3866415135f457200128e2812onquest/a1/rind/noq. Focused command output is retained in the checkout's.tmp/.Review
Cross-vendor review is deferred: this is an incomplete migration with a reproduced handshake failure. Finish checks and review the committed head after the stable upstream dependency is available; keep the PR draft.
Recommended follow-up
Implement, test and publish rind-rustls's path-aware packet encryption/decryption upstream, including path 0 and nonzero path IDs for all three TLS 1.3 suites. Resume this migration on that stable version. No new quest or issue was created.
(Written by GPT-6.1 Sol with xhigh)