Repository navigation
Conversation
This was referenced Oct 13, 2026
iuyo5678
added this pull request to stack #433
October 13, 2026 13:52
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
2 participants
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.
Authenticate local WebSocket peers before any browser registration, session purge, audit access, or tool dispatch. The prelude verifies both HMAC proofs, binds the browser identity, and durably commits activation/rotation before allowing the business handshake. Recovery uses the saved candidate key and emits one final message.
The local listener bounds unauthenticated connections, upgrade/prelude time, and message size before payload allocation. Device authentication is serialized, activation conflicts are disclosed only after proof, and local/remote authorization share the business connection driver. Existing browser simulations explicitly select trust-local mode.
Validation: ten real WebSocket authentication tests cover missing/wrong credentials, replay, busy devices, immediate invalidation of the pairing link, interrupted rotation/recovery, replacement and mismatch, staged replacement recovery, identity binding, final-message handling, and legacy policy combinations. Header-limit and storage tests, workspace Clippy, and the full Rust regression suite also pass.
Stack 3/9 — depends on #425. Default policy remains warning mode. The next PR synchronizes final browser registration with revocation and adds status/doctor guidance.
Stack order: #424 → #425 → #426 → #427 → #428 → #429 → #430 → #431 → #432. Each PR targets the preceding branch; PR8 and PR9 retain their release prerequisites.