Conversation
JkLondon
force-pushed
the
jklondon/reality-clienthello-auth
branch
from
September 29, 2026 17:04
30f4efd to
b598a48
Compare
JkLondon
marked this pull request as ready for review
September 29, 2026 21:29
Member
|
？ |
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.
I want to split the REALITY handshake implementation into two parts: X25519 key agreement and ML-DSA signing which would be performed by two separate entities. I would appreciate it if you would consider this small architectural PR that only separates ClientHello verification from the rest of the server handshake