Add Chrome 153 ClientHello profile - #420
Open
wywywywycloud wants to merge 1 commit into
Open
wywywywycloud wants to merge 1 commit into
wywywywycloud wants to merge 1 commit into
Conversation
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
1 participant
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.
Summary
HelloChrome_153and updateHelloChrome_Autosignature_algorithmswith a leading GREASE value and ML-DSA-44/65/87trust_anchorsextension (0xca34) and update GREASE seed handlingFixes #397.
Verification
go test ./...go test -race ./...go vet .trust_anchorson the wire asca34 0002 0000, a randomized GREASE signature scheme, and ML-DSA schemes0904,0905, and0906Scope and limitations
This fixes a specific, measured ClientHello mismatch; it does not claim complete undetectability.
Chrome's
trust_anchorsbehavior is feature- and platform-dependent. This profile matches captures where the feature is enabled and Chrome sends an emptyRequestedTrustAnchorList.The ML-DSA codepoints are advertised for ClientHello fingerprint parity. uTLS does not currently implement ML-DSA certificate-signature verification, so a server that selects an ML-DSA-only certificate chain can still fail the handshake.