[1.78.0] - 2026-08-17
- FIXED: Traffic that merely used port 53 was read as a name lookup - a VPN or proxy tunnel hidden on that port had its encrypted contents taken for a domain name and matched against sets.
- FIXED: The server name read out of a QUIC connection was accepted whatever it contained - any bytes of any length passed for a hostname, unlike the same name read from an ordinary HTTPS connection, which was checked.
- FIXED: Telegram reported the MTProto proxy as incorrectly configured and switched it off - a session was accepted before b4 had reached a data center, and one blocked route was given longer than the client was willing to wait.
- FIXED: Data center 203 had no connection ready in advance - spare connections were kept for two data centers only, so every session on the others started by opening one from scratch.
- FIXED: A route that answered nothing was set aside only when it replied with a rate limit - a route that went silent cost every session after it the same full wait.
- FIXED: A name with several addresses was abandoned after the first one went unanswered - the attempt stalled on that address while another address of the same name answered in under a second.
What's Changed
- 1-78-fix by @DanielLavrushin in #311
Full Changelog: v1.77.0...v1.78.0rc1