Repository navigation
Bump rtc-ffi-bindings to 0.13.2 (drop compromised eMudhra roots) - #766
Open
erikhortsch wants to merge 1 commit into
Open
erikhortsch wants to merge 1 commit into
erikhortsch wants to merge 1 commit into
Conversation
livekit-ffi 0.13.2 builds against libwebrtc webrtc-a545de4, whose compiled-in TURN/TLS roots no longer include AAA Certificate Services, the root that cross-signs the compromised eMudhra intermediates. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BsJ5Refi6x7GqXMqH4gJ4i
🦋 Changeset detectedLatest commit: 7302f70 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
erikhortsch
marked this pull request as ready for review
October 23, 2026 16:39
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
packages/livekit-rtc/package.json:@livekit/rtc-ffi-bindings0.13.1→0.13.2.pnpm-lock.yaml: regenerated withpnpm install --lockfile-only(pnpm 10.18.2). Only thertc-ffi-bindingsentries change..changeset/rtc-ffi-0-13-2-emudhra-roots.md: patch changeset for@livekit/rtc-node.This follows the same shape as #748 (the 0.13.1 bump).
Why
On 2026-10-20 the keys of eight eMudhra intermediate CAs were disclosed as compromised. They are cross-signed by
AAA Certificate Services.rustls-webpki/webpki-roots), which covers the signal connection.rtc_base/ssl_roots.h). livekit-ffi 0.13.1 still builds againstwebrtc-89d790b, whose list includes AAA.webrtc-a545de4, whose refreshed roots drop AAA.0.13.2 also carries the other fixes in its changelog: the capture error
kind, the VAAPI parameter-buffer leak and the NVENC/Jetson delivered-frame error. The FFI protocol change between 0.13.1 and 0.13.2 is additive only (CaptureError.kindincapture.proto).Testing
pnpm build:livekit-rtc: passes.pnpm --filter @livekit/rtc-node test: 6 files passed, 63 tests passed. The e2e suites are skipped locally because they need a server.pnpm --filter @livekit/rtc-node lint: no new findings. The 11 existing warnings are in files this PR does not touch.Release
After merge, the changesets action opens or updates the "Version Packages" PR. Merging that publishes
@livekit/rtc-node.Generated by Claude Code