OnceUponATimeInAmerica

Yes, It really seems so. A MITM attack, a kind of forced downgrade of TLS, a new side-channel attack which does not target the circumvention protocols or (blocking) the servers...

> Is this help for you? `v2rayN `on Windows works fine without setting that option. Using traffic capture I found out it defaults to TLS v1.2 _without_ that option set...

This seems very relevant to the present issue: Curiously, [this](https://github.com/net4people/bbs/issues/129) reported development in China's GFW coincides almost exactly both in time and techniques with the new restrictions in Iran's filtering...

> Try https://github.com/MatsuriDayo/Matsuri/actions/runs/3214534575 > > There is a TLS Version option. > > If this doesn't work, send the pcap of this and v2rayN. Thank you. The subscription update now...

> It seems there is no such option for v2ray-core. I switched the core in `v2rayN `(desktop) from `xray `to `v2fly` (`v5.1.0`) and it uses TLS v1.2 (for everything) and...

I only found this in the official v2ray [docs](https://guide.v2fly.org/en_US/advanced/wss_and_web.html#client-side-configuration): > Note that: V2Ray supports TLS1.3 since 4.18.1. If you enable and force TLS1.3, please check the v2ray client version. And...

The problem was solved, at least temporarily, by enabling "browser forwarding" in v2ray-core options for the relevant Vmess+ws+tls (etc.) server. The only drawback is that this setting needs to be...

> I assume you mean as clients for v2ray-type protocols. v2rayNG and Matsuri work good for me; Latest builds of both; In v2rayNG you might need to enable uTLS custom-fingerprint...

You have to tell them you want an explicit TLS v1.3 for everything (subscription update, server testing and connection) setting in the UI.

This is most probably a TLS fingerprinting-based blocking. One workaround which I found, for vmess+ws+tls servers is to enable "browser forwarding" option in the v2ray-core client. I don't know if...