This repository was archived by the owner on Apr 5, 2026. It is now read-only.
Commit 052f718
committed
fix: propagate client transport tag to DC in direct mode (#64)
The proxy always sent 0xeeeeeeee (intermediate, no padding) in the
obfuscated2 init to Telegram DCs, regardless of what the client used.
When clients use 0xdddddddd (random padding) — which ALL clients do
(both dd-prefix and ee-prefix modes) — the DC received padded messages
but expected non-padded, causing parse errors and silent failures.
Fix: store the client's transport tag in extra_int3 and propagate it
through direct_connect_to_dc to tcp_direct_dc_connected, which now
uses it in the DC-bound init instead of the hardcoded 0xeeeeeeee.
Closes #641 parent e69983a commit 052f718
2 files changed
Lines changed: 11 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
173 | 173 | | |
174 | 174 | | |
175 | 175 | | |
176 | | - | |
| 176 | + | |
177 | 177 | | |
178 | 178 | | |
179 | 179 | | |
180 | 180 | | |
181 | | - | |
| 181 | + | |
182 | 182 | | |
183 | 183 | | |
184 | 184 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
319 | 319 | | |
320 | 320 | | |
321 | 321 | | |
322 | | - | |
323 | | - | |
| 322 | + | |
| 323 | + | |
| 324 | + | |
| 325 | + | |
| 326 | + | |
| 327 | + | |
324 | 328 | | |
325 | 329 | | |
326 | 330 | | |
| |||
415 | 419 | | |
416 | 420 | | |
417 | 421 | | |
418 | | - | |
| 422 | + | |
419 | 423 | | |
| 424 | + | |
420 | 425 | | |
421 | 426 | | |
422 | 427 | | |
| |||
1608 | 1613 | | |
1609 | 1614 | | |
1610 | 1615 | | |
| 1616 | + | |
1611 | 1617 | | |
1612 | 1618 | | |
1613 | 1619 | | |
| |||
0 commit comments