[1.82.0] - 2026-09-12
- ADDED: A set can be handed to another b4 user as a shared set - with community sets switched on under Settings, Integrations, the set editor's Import/Export tab prepares one from an allow-list that keeps the strategy, the targets, the DNS redirect and block-mode routing, leaves out and names everything tied to the router, and carries the set's payload files inside, where the plain export copied an enabled routing block verbatim, upstream credentials included, and a set naming a payload file the receiver lacked silently ran a built-in one. A shared set pasted into Import is checked on the router, its payload files are installed, settings this b4 does not know and categories its geosite lacks are reported, and the set card shows whether the imported strategy has been edited since.
- ADDED: A QUIC handshake can be sent behind a padding packet inside the same datagram - the new
coalesceUDP mode builds a padding-only QUIC Initial, encrypted under the keys derived from the connection's own identifier, and puts it ahead of the client's Initial in one datagram, leaving the handshake itself byte for byte unchanged. - ADDED: A plain HTTP request can carry an empty line before its method - the new
http_methodeolTCP option prepends an empty line to the request line and takes two characters off the end of theUser-Agentvalue, so the request keeps its exact length and the client's sequence numbers stay correct. A server ignores the empty line, while inspection that expects the method at the start of the request stops finding theHostheader. It needs aUser-Agentheader, covers port 80 only and suits nginx origins. Before this, b4 could not alter an HTTP request at all, so a site filtered by itsHostheader had nothing that worked. - ADDED: The Telegram WEB proxy can have a port of its own, and its placeholder page can be replaced - under Settings, MTProto Proxy, Telegram Desktop WEB proxy, a relay port opens a separate listener that answers the relay hostname as the relay and every other name or IP address with the placeholder, with a certificate of its own so the interface can stay plain HTTP on the LAN, so a router forward from WAN 443 no longer has to land on the web interface's port, where
https://<public IP>/showed the b4 login page next to the relay. The placeholder itself, one "Service status" page identical on every installation, can be replaced by uploading a self-contained HTML file in the same card. - FIXED: Discovery could name a winning strategy for a site that stays blocked, and searched two families with a fake it had already proved harmful - a reply of HTTP 400 counted as a working fetch, although a Bad Request is the strategy under test mangling its own request, and a 157-byte error page reached the finish line because it ended in the usual closing tags; separately, the TTL sweep reports nothing when every value fails, and the caller answered that by picking 7 and carrying on, so the TCP-fragmentation and TLS-record searches were measured with a fake the censor had just been shown to punish.
What's Changed
- fix(daemon): make shutdown killable and actually bounded by @DanielLavrushin in #352
- chore: update changelog for version 1.81.1 release by @DanielLavrushin in #354
Full Changelog: v1.81.0...v1.82.0rc1