True End-to-End Encryption with Insertable Streams

The Broken Trust Model of Standard SFU Encryption

Insertable Streams introduce a new paradigm in WebRTC architecture, enabling true end-to-end encryption. This technology allows for the encryption of media payloads, making it impossible for SFUs to access the content.

Why This Matters

The standard WebRTC architecture relies on DTLS-SRTP, which introduces a critical compromise in the trust model: the Privileged Decryption Point. This means that SFUs can access the media content, posing a significant security risk. Insertable Streams address this issue by enabling true end-to-end encryption, ensuring that only the intended recipients can access the content.

Key Insights

• Insertable Streams use the WebRTC Encoded Transform API to intercept and encrypt media payloads (WebRTC API, 2022)
• ECDH key exchange is used to establish shared secrets between participants (RFC 6090, 2011)
• AES-GCM is used for payload encryption, providing authenticated encryption (NIST, 2007)

Working Examples

Sender-side setup for Insertable Streams

// main.js - Sender Side setup
const pc = new RTCPeerConnection(config);
const sender = pc.addTrack(track, stream);
// 1. Force the specialized API for encoded transforms
if (sender.createEncodedStreams) {
  // Read the encoded streams
  const streams = sender.createEncodedStreams();
  // 2. Initialize the Crypto Worker
  const worker = new Worker("crypto-worker.js");
  // 3. Define the encryption configuration (e.g., Key ID, algorithm)
  const meta = {
    operation: 'encrypt',
    participantId: 'user-1234',
    keyId: currentKeyId
  };
  // 4. Transfer the streams to the worker
  // We use postMessage with transferables to zero-copy move the streams
  worker.postMessage({
    operation: 'encrypt',
    readable: streams.readable,
    writable: streams.writable,
    config: meta
  }, [streams.readable, streams.writable]);
} else {
  console.error("Insertable Streams not supported in this browser.");
}

Practical Applications

• Telehealth platforms can use Insertable Streams to ensure HIPAA compliance (e.g., Doctor-Patient consults)
• Financial institutions can use Insertable Streams to secure sensitive video conferences (e.g., Board meetings)

References:

• https://dev.to/deepak_mishra_35863517037/trust-no-one-implementing-true-end-to-end-encryption-with-insertable-streams-2ndk