Repository navigation
Conversation
This was referenced Oct 13, 2026
iuyo5678
force-pushed
the
feat/local-pairing-03-handshake
branch
2 times, most recently
from
November 2, 2026 06:59
09cc85b to
a4cd820
Compare
iuyo5678
force-pushed
the
feat/local-pairing-03-handshake
branch
from
November 2, 2026 10:18
a4cd820 to
34d0075
Compare
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.
Support optional local authentication before browser registration and business traffic. Paired peers prove their local keys, while Warn-mode daemons accept existing extension handshakes. Required mode remains an explicit policy choice.
The protocol validates proofs, identity binding, rotation and saved-candidate recovery before granting authenticated access. The later paired-identity protection PR prevents legacy peers from impersonating an activated browser while keeping unrelated unpaired browsers usable.
Validation across the final stack:
Stack 3/9; base: #425. Review order: #424 → #425 → #426 → #427 → #428 → #429 → #430 → #431 → #432.