[docs] update information about TLS fingerprint in FAQ

Updated information about TLS fingerprint issue and notice for users to update their clients
This commit is contained in:
Nick Parfyonov
2026-04-14 14:26:12 +03:00
parent 286662fc51
commit f0ebbac338
2 changed files with 10 additions and 4 deletions

View File

@@ -36,8 +36,11 @@ hello2 = "ad_tag2"
On April 1, 2026, we became aware of a method for detecting MTProxy Fake-TLS,
based on the ECH extension and the ordering of cipher suites,
as well as an overall unique JA3/JA4 fingerprint
that does not occur in modern browsers:
we have already submitted initial changes to the Telegram Desktop developers and are working on updates for other clients.
that does not occur in modern browsers.
> [!IMPORTANT]
> TLS fingerprint has been fixed in latest version of clients for Desktop / Android / iOS.
> Please update your cleint for MTProxy Fake-TLS to work correctly.
- We consider this a breakthrough aspect, which has no stable analogues today
- Based on this: if `telemt` configured correctly, **TLS mode is completely identical to real-life handshake + communication** with a specified host