Repository navigation
docs(xray): date the client compatibility check - #9
Merged
Merged
Conversation
Client compatibility is a point-in-time result: a new Xray, uTLS or sing-box release can change it. The section now carries the date and versions of the check, names the X25519MLKEM768 requirement of the Reality server since Xray 26.9.8, and the client-core threshold for the firefox template (26.3.27). Which fingerprint suits a given network is a deployment choice and stays out of the repo.
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.
Problem
The client compatibility section stated measured results as timeless facts and did not explain why only some fingerprints pass Reality. The Reality server rejects a ClientHello without an
X25519MLKEM768key share since Xray 26.9.8, and older client cores sendfirefoxwithout it.What changed
docs/xray.md, section "Client compatibility": a dated anchor line with the checked versions, the server's key-share requirement, usher's fingerprint enforcement, the client-core threshold (26.3.27) forfirefox, and the sing-box results. No per-network fingerprint advice.Verification
docs/plans/completed/20261014-xray-config-backend.md:86-102), the 2026-10-15 measurement on rem with an Xray-core 26.1.23 client, and the uTLS sources pinned by Xray v26.1.23 (HelloFirefox_Auto = HelloFirefox_120) and v26.3.27 (HelloFirefox_148).scripts/format.shpasses.Per-task commits before collapse