Repository navigation
Conversation
|
@up1and is attempting to deploy a commit to the 7sageer's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Motivation
mihomo adds a mihomo-only option
reality-opts.support-x25519mlkem768(https://wiki.metacubex.one/en/config/proxies/tls) to keep X25519MLKEM768 in the REALITY ClientHello key share. REALITY servers on Xray-core v25.5+ require this key share, so dropping the field breaks the converted node entirely.The flag only exists as a mihomo YAML field; there is no official vless:// URI parameter, but some panels already emit a de-facto
support-x25519mlkem768=truequery param in share links. Both input forms were silently discarded by the whitelist-style parsing.Related: #417 (post-quantum field loss during conversion)
Changes
src/utils.js#createTlsConfig): readsupport-x25519mlkem768=truequery param forsecurity=reality(vless/trojan and other URI parsers sharing this path)src/parsers/convertYamlProxyToObject.js): mapreality-opts.support-x25519mlkem768for vless/trojan into the internaltls.reality.support_x25519mlkem768src/builders/ClashConfigBuilder.js): emitreality-opts.support-x25519mlkem768(vless/trojan); omitted when unsetsrc/builders/SingboxConfigBuilder.js): strip the flag — sing-box rejects unknown fields, and since 1.13 it already enables X25519MLKEM768 in its defaultcurve_preferences, so no equivalent option is neededtest/reality-mlkem768.test.jscovering both input paths, mihomo output roundtrip, and sing-box stripping (incl. no-mutation of the source object)Verification
npm test— 39 files / 301 tests pass.