Beta Update - TLS Client Fingerprint
Proxies over TLS can now reproduce the TLS ClientHello of a real client, with the new
•
•
•
It applies to HTTPS, SOCKS5-TLS, HTTP/2 CONNECT, Trust Tunnel, Trojan, AnyTLS, and VMess/VLESS with TLS or REALITY. The
Surge's TLS is built on BoringSSL, the same library Chrome uses, and Apple's TLS stack runs on its own fork of it. The fingerprints therefore come from the library itself rather than from a template: GREASE values, extension order and ECH GREASE are generated the same way as in the original clients, and the rest of the handshake follows the same code.
Proxies over TLS can now reproduce the TLS ClientHello of a real client, with the new
client-fingerprint parameter:•
apple-26: Apple's system TLS stack, as sent by Safari and by apps using NSURLSession: iOS 26–27, macOS 26–27, Safari 26–27•
chromium-155: Chrome 155–158 and the browsers built on Chromium•
auto (default): The recommended fingerprint, currently apple-26Proxy = trojan, example.com, 443, password=pwd, client-fingerprint=chromium-155It applies to HTTPS, SOCKS5-TLS, HTTP/2 CONNECT, Trust Tunnel, Trojan, AnyTLS, and VMess/VLESS with TLS or REALITY. The
fp value of a share link is converted automatically. Since auto is the default, every TLS proxy now looks like Apple's system traffic out of the box; use none to keep the old behavior.Surge's TLS is built on BoringSSL, the same library Chrome uses, and Apple's TLS stack runs on its own fork of it. The fingerprints therefore come from the library itself rather than from a template: GREASE values, extension order and ECH GREASE are generated the same way as in the original clients, and the rest of the handshake follows the same code.
- 👍3