Repository navigation
feat: add HelloChrome_155 and make it HelloChrome_Auto - #4
Merged
Merged
Conversation
Port the Chrome 155 profile from refraction-networking/utls 6ebdceb ("Add Chrome 155 fingerprint verified against a fresh browser capture"), verified there against Chrome 155.0.8059.40. Compared with Chrome 133 the ClientHello gains a GREASE value and the three ML-DSA schemes (0x0904/0x0905/0x0906) in signature_algorithms and the trust_anchors extension (0xca34) with 28 Chrome Root Store IDs. - HelloChrome_155 and its spec; HelloChrome_Auto now points to it, as upstream does. HelloChrome_133 is unchanged. - TrustAnchorsExtension (typed, JSON, Fingerprinter via ExtensionFromID). - GREASE in signature_algorithms drawn from its own BoringSSL seed slot; the internal seed grows to 8 slots while GetBoringGREASEValue keeps its [5]uint16 signature. - MLDSA44/65/87 SignatureScheme constants and dicttls names. Unlike upstream (go 1.27 sync) this fork does not implement ML-DSA, so the codepoints are only advertised. - Upstream tests and the captured ClientHello fixture. Not ported: the ML-DSA handshake test (needs crypto/mldsa) and the preset ownership test (needs upstream's ClientHelloSpec.clone).
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.
Ports the Chrome 155 profile from refraction-networking/utls 6ebdceb ("Add Chrome 155 fingerprint verified against a fresh browser capture", verified there against Chrome 155.0.8059.40 on macOS). Needed for Citrus to make
client-fingerprint: chromemean Chrome 155, as Xray-core 26.11.9 did.What changes on the wire (vs Chrome 133)
signature_algorithms: a GREASE value first, then ML-DSA-44/65/87 (0x0904/0x0905/0x0906), then the old eight schemes.trust_anchorsextension (0xca34) with the 28 Chrome Root Store IDs from the capture.Changes
HelloChrome_155+ spec inu_parrots.go;HelloChrome_Autonow points to 155 (upstream did the same).HelloChrome_133is untouched.TrustAnchorsExtension(u_trust_anchors.go), wired intoExtensionFromID, so the Fingerprinter and JSON give a typed extension.signature_algorithmsnow uses its own BoringSSL seed slot (slot 7). The internal seed array grows to 8 slots. The exportedGetBoringGREASEValue([5]uint16, int)keeps its signature.MLDSA44/65/87SignatureSchemeconstants (+ stringer output) and dicttls names. Difference from upstream: upstream had real ML-DSA support from its go 1.27 sync. This fork does not, so the codepoints are only advertised. If a server ever picked ML-DSA, the handshake would fail with "unsupported signature algorithm". REALITY/JLS servers and normal web servers do not pick it.Tests
Ported from upstream: the captured ClientHello fixture (
testdata/chrome155_clienthello.hex, 1955-byte record) compared with the generated hello (normalizing only GREASE, extension order, key material and ECH randomness), the Fingerprinter round-trip, the signature-GREASE seed slot, Chrome 133 unchanged, the trust-anchors encode/decode/JSON/limits checks, ML-DSA JSON names, and the GREASE public API.Not ported:
TestChrome155MLDSAHandshake(needscrypto/mldsa) andTestChrome155PresetOwnership(needs upstream'sClientHelloSpec.clone, which this fork doesn't have; the fresh trust-anchor slices are still returned per spec).go test ./...andgo vetpass with go1.26.10 (windows/amd64).Cross-check: the fixture is byte-identical to the one in Rerowros/veles (
component/tls/testdata/chrome155_clienthello.hex), and that project's hand-written spec has the same contents. It is the same capture, though, not an independent one.