Zachary AnyTLS 是一个用于缓解 TLS in TLS 特征的协议。 引用一下作者的原话： Why we need this protocol? This is a concise and clear "Any in TLS" proxy protocol. This means you can ship anything on top of TLS without having to worry about firewalls identifying it due to some side-channel leak. It provides functions for modifying packet length characteristics, which are not available in previous protocols. It is well known that simpler protocols, such as Trojan, are already fully recognized by the GFW due to the side-channel leak so-called "TLS in TLS problem". Even with multiplexing or hard-coded padding, it still produce very fixed packet length characteristics (when you carry TLS on it). We also took the handshake RTT into consideration, so we implemented connection reuse, but it is not like sing-mux or other earlier mux, because it only carries one stream on a single connection at the same time, so there is no head-of-line blocking problem. All in all, this is a protocol with clear semantics, forward-looking design, and excellent performance. (...) https://github.com/anytls/anytls-go
love4taylor Ader stls 尴尬的是只支持 tcp based 的代理协议，snell 又不是全平台通用。配 ss2022 的话 udp 部分又是露在外面的，配 trojan 的话两层太重了，配 vmess 的话协议本身的 udp 就是屎，总结除非果子全平台用户，否则 stls 在 surge 上用起来挺不爽的。
lorem233 AIEPhoenix 详见： https://community.nssurge.com/d/931-surge https://community.nssurge.com/d/3744-shadowsockssnelltrojan/3#:~:text=SystemAdministrator-,我们有在关注%20AnyTLS，据悉可能要进行一次重构更新，所以可能等待后续直接支持新版 然后在上周在AnyTLS的V3计划里面，看到了AnyTLS作者的回复 https://github.com/anytls/anytls-go/issues/19#issuecomment-3562904028 个人建议： 趁着黑五余热买机器玩自建snell～
aaron Version 6.4.3 Build 9850 2025年12月11日 Changes Support for a new proxy protocol: AnyTLS. (UDP forwarding support is not yet complete)
