[1.82.0] - 2026-09-15
- ADDED: Community Hub: a set can be published to hub.b4core.app, and sets other b4 users published can be browsed, applied and rated from a new Community page - a shared set carries only the strategy, its targets and its payload files, leaves out everything tied to the router, waits for a moderator before it appears, and stays linked once applied so it can be rated, updated or reported, while Discovery tries community sets for a domain before its own presets. It sits behind one switch under Settings, Integrations, off by default, and the
b4hubservice that ships alongside runs a self-hosted hub or a mirror of the central one, with the daily limits per contributor set from its moderation console and trusted keys exempt from them. - ADDED: A QUIC handshake can be sent behind a padding packet inside the same datagram - the new
coalesceUDP mode puts a padding-only QUIC Initial, encrypted under the connection's own keys, ahead of the client's Initial in one datagram and leaves the handshake itself unchanged. - ADDED: A plain HTTP request can carry an empty line before its method - the new
http_methodeolTCP option prepends the line and trims theUser-Agentvalue by two characters so the request keeps its length, and inspection that expects the method first stops finding theHostheader. It covers port 80 only and needs aUser-Agentheader; before it, a site filtered by itsHostheader had no strategy at all. - 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 with its own certificate that answers the relay hostname as the relay and everything else with the placeholder, for a WAN 443 forward that otherwise landed on the web interface and showed the b4 login page at
https://<public IP>/. The placeholder 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 kept searching with a fake it had already proved harmful - an HTTP 400 and a 157-byte error page both counted as a working fetch, and when every TTL failed the sweep fell back to 7 and measured the TCP-fragmentation and TLS-record families with it.
- FIXED: A passphrase-protected TLS key was accepted under Settings, and the web interface silently stayed on plain HTTP - saving only checked that the two files existed, the failed load at start was a warning that reached neither the error log nor the dashboard, and a certificate file missing at start stopped the service altogether.
- CHANGED: A Discovery run stopped early confirms what it has found instead of leaving it unconfirmed - Stop and confirm ends the search at the current preset, marks the remaining steps skipped and runs the confirmation pass on the winners so far, and a second press during confirmation ends the run at once. Before, the only stop kept an unconfirmed result, the one kind the confirmation pass exists to catch.
- CHANGED: "Match Fake Size" copies the real ClientHello into the fake instead of stretching the payload to its size - only the domain name is overwritten, fitted to the real name's length, and Discovery tries this shape with an old TCP timestamp or a bad checksum at full TTL. On two Russian networks the filter drops a fake that differs from the real greeting by a single byte of length and passes one of equal length, while the stretched fake repeated the payload's bytes and was no ClientHello at all.
- CHANGED: The set comparison dialog is rebuilt around the same Target, Split, Fake, Route, DNS and Escalate rows as the set cards - both sets are picked and swapped inside the dialog, every differing row carries its setting name, targets are compared by category and domain instead of by count, and a "Differences only" switch hides what matches. The old dialog opened as a narrow column and hid the setting names in truncated chips. #356
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.0rc2