From 397ed8f1936de225deabd1144d3490433aa70e82 Mon Sep 17 00:00:00 2001 From: Alexey <247128645+axkurcom@users.noreply.github.com> Date: Thu, 22 Jan 2026 01:56:42 +0300 Subject: [PATCH] Update README.md --- README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 133f002..94c18a8 100644 --- a/README.md +++ b/README.md @@ -254,13 +254,12 @@ we transparently direct traffic to the target host! - 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 - Here is our evidence: - - 212.220.88.77 - "dummy" host, running `telemt` - - `petrovich.ru` - `tls` + `masking` host, in HEX: `706574726f766963682e7275` - - client WITH secret-key accesses the MTProxy resource: + - 212.220.88.77 - "dummy" host, running `telemt` + - `petrovich.ru` - `tls` + `masking` host, in HEX: `706574726f766963682e7275` + 1) client WITH secret-key accesses the MTProxy resource: telemt - - - client WITHOUT secret-key gets transparent access to the specified resource: + 2) client WITHOUT secret-key gets transparent access to the specified resource: - with trusted certificate - with original handshake - with full request-response way