naughtysoul/telemt
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Alexey
2026-01-22 01:56:42 +03:00
committed by GitHub
parent d90b2fd300
commit 397ed8f193
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@@ -254,13 +254,12 @@ we transparently direct traffic to the target host!
- We consider this a breakthrough aspect, which has no stable analogues today - 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 - 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: - Here is our evidence:
- 212.220.88.77 - "dummy" host, running `telemt` - 212.220.88.77 - "dummy" host, running `telemt`
- `petrovich.ru` - `tls` + `masking` host, in HEX: `706574726f766963682e7275` - `petrovich.ru` - `tls` + `masking` host, in HEX: `706574726f766963682e7275`
- client WITH secret-key accesses the MTProxy resource: 1) client WITH secret-key accesses the MTProxy resource:
<img width="360" height="439" alt="telemt" src="https://github.com/user-attachments/assets/39352afb-4a11-4ecc-9d91-9e8cfb20607d" /> <img width="360" height="439" alt="telemt" src="https://github.com/user-attachments/assets/39352afb-4a11-4ecc-9d91-9e8cfb20607d" />
2) client WITHOUT secret-key gets transparent access to the specified resource:
- client WITHOUT secret-key gets transparent access to the specified resource:
- with trusted certificate - with trusted certificate
- with original handshake - with original handshake
- with full request-response way - with full request-response way