Repository navigation
Robotweax SRT 0.3.3 — Hybrid Multicast and Transport Hardening
Robotweax SRT 0.3.3 adds opt-in independent-source and coordinated IPv4 multicast, a default-off experimental hybrid control profile with unicast fallback and multicast return, and transport hardening in key rotation, authenticated decryption and listener lifecycle.
Release status
Final-tag CI, package qualification, the protected independent rebuild and signing are complete. The OpenSSL and BCrypt Windows SDK installers are Authenticode-signed by Robotweax GmbH. Their downloaded bytes match the signed CI artifact and the attached SHA256SUMS manifest; tag provenance has been verified.
Changes
- Independent-source IPv4 multicast separates the fixed multicast source from the per-receiver control connections. The opt-in coordinated sender owns original emission, canonical recovery history and an aggregate wire budget; it requires a positive
SRTO_MAXBWand supports at most 64 receivers. - The experimental hybrid control profile adds pairwise authenticated startup, bounded membership recovery, unicast fallback and multicast return. It requires the explicit ACP1 and HYBRID_CONTROL build options, both default-off. The multicast media sample accepts
--hybridin a static enabled build. No public hybrid C API is introduced. - An ordinary multicast dispatch sender with a positive group
SRTO_MAXBWnow limits the unicast repeats of all its members together to four times that rate. Groups without a positive rate behave as before. - Delayed DATA arriving after a receive-key replacement is routed by accepted sequence position, so a long burst loss or delay no longer decrypts retired-generation packets with the replacement key. Retired generations expire before sequence reuse.
- A failed authenticated open preserves ciphertext and tag, including with an overlapping destination buffer, and never publishes unauthenticated output.
- Overdue timers can no longer starve listener-close work. Multicast socket profiles are revalidated at listen commit, and superseded routes are retired only when their binding still matches.
- On Windows the runtime scheduler holds a one-millisecond timer period for its lifetime. Build with
ROBOTWEAX_SRT_WINDOWS_TIMER_PERIOD=OFFto leave timer resolution to the application. - The Linux readiness watcher copies each epoll payload before use, removing a reference to a packed, misaligned field.
Compatibility and scope
Project version 0.3.3, shared-library ABI 0.3, compatible SRT API 1.5.7. All 85 C exports and the existing public C layouts of 0.3.2 remain. New socket options require matching headers and library. Native source-tree C++ consumers must rebuild against matching sources; ABI 0.2 applications also require rebuilding.
Hybrid control is experimental and outside the supported security and Haivision interoperability boundary. Its fallback uses a live catch-up policy that can discard unread buffered media and reports the skipped positions; it is not a lossless failover or decoder-continuity guarantee. Multicast remains limited to explicitly trusted groups: shared keys provide neither exclusive sender identity against other key holders nor cryptographic revocation on receiver departure. Loopback qualification does not establish physical multicast/IGMP, WAN, fan-out or general throughput guarantees.
See the complete release notes, connection groups, experimental hybrid control, 0.3.3 security delta and release contract.
Source and qualification
- Release commit:
69bd5328bf654ebbed894c77fd30ae5b2dfba9d7. - Immutable product archive:
f5948a4b059aa1c8e7aa5e932053f92ff37eb6ff, the fourth frozen product. - Archive SHA-256:
ccc2c409790f0d72bedbc7f87ebeb429fe723716af3b30bdd87f52fbc3d79ec7. - Pre-tag full CI passed on the first attempt on the recipe commit (43383119151) and on the merged head (43388422357), including the media integrations and all OBS platform jobs.
- Exact-archive Linux packages and package managers, and the exact-product Lab smoke, interop and telemetry requests passed. A commit-bound local macOS hybrid soak passed.
- Two residual risks were accepted and are not marked fixed: the historical macOS identity-rendezvous timeout, and an intermittent OBS desktop reconnect failure in the test fixture, for which a crash in the pinned OBS reconnect path was identified and corrected in the fixture.
- Three hosted first failures have no measured cause and stay recorded: a macOS group receive timing assertion, a macOS UDP bridge connection timeout and an Ubuntu Debug runner shutdown during a parallel build.
- The full record, including every superseded product and first failure, is in
packaging/qualification-0.3.3.mdandpackaging/acceptance-0.3.3.json.
Final-tag release evidence
- Full source CI and Required CI gate passed on the release commit.
- Package-manager qualification and Linux package qualification passed.
- Windows SDK qualification, protected rebuild, signing and release draft passed in one workflow attempt. Exactly one protected independent rebuild ran; the optional unsigned rebuild diagnostic was skipped.
- Both downloaded release installers and
SHA256SUMSmatch signed CI artifact14029517334byte-for-byte. GitHub asset digests and both installer checksums also match. - The unchanged annotated tag object is
29c741d35f89a412926c374d6ccb15fa1270833c;tag-provenance.jsonbinds it to the release commit. Use the attachedSHA256SUMSto verify installer downloads.