Repository navigation
End-to-end encrypted voice and video calls on PairUX (0.4.0, qc 0.4.0) - #281
Merged
Merged
Conversation
The header's call buttons drove an MLKEMCallManager built with a null WebSocket (signalling on the server the app no longer runs), so calls were dead. They now run on PairUX's SFU through @profullstack/pairux-embed with LiveKit E2EE: - Starting a call makes a fresh 32-byte media key and sends it to the conversation in a message of type 'call' whose body is ML-KEM-1024 encrypted per participant, like any message. Neither qrypt's server nor PairUX ever holds the key; every frame is encrypted in the browser. - POST /api/calls/token: checks you are in the conversation, then asks PairUX for a token with qrypt's partner key (PAIRUX_PARTNER_KEY, server only). Room = conversation id. - CallPanel overlay mounts the PairUX widget (tiles, mic/camera/screen/ leave); a browser that cannot encrypt is told so, never downgraded. - Call invites render as "📞 Alice started a voice call · Join" cards (joinable for 6h); qc shows them as text and never prints the key. - Migration 20261006200000: message_type 'call' (applied on dev2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan13 finding(s) MEDIUM: 9 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
Contributor
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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
1 participant
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.
Problem: the header's voice and video call buttons drove an
MLKEMCallManagerbuilt with a null WebSocket. Its signalling lived on the WebSocket server the Next app no longer runs, so calls were dead.Fix: calls now run on PairUX's SFU through
@profullstack/pairux-embed(profullstack/pairux.com#133), with LiveKit end-to-end encryption.How the key moves
callmessage whose body is ML-KEM-1024 encrypted per participant, the same as any message.Server:
POST /api/calls/tokenchecks the caller is a participant, then asks PairUX for a token with qrypt's partner key. The key (PAIRUX_PARTNER_KEY) lives only on the server, inapp.envand the vault. The room is the conversation id, in PairUX'spartner-qrypt-*namespace, which PairUX never records or analyses.UI
CallPanelis an overlay hosting the PairUX widget: tiles, mic, camera, screen share and leave, with 🔒 shown per participant.qc: shows invites as text and never prints the key. A test covers this.
Migration:
20261006200000_message_type_call, already applied on dev2.Verification
test:ci: 647/647.next buildpasses and emits the E2EE worker chunk (checked).Not covered yet
🤖 Generated with Claude Code