FEAT | PQ Media Streams

[sevenbitbyte]

🚀 Feature Proposal

Research ability to post-quantum encrypt WebRTC media streams.

This looks obviously very solvable in native (non browser) WebRTC api's bc they provide direct access to change the underlying DTLS ciphers. The browsers don't seem to have much support for this.

We've found several possible solutions with various tradeoffs:

• Use AES256 or AES512 for media stream - Only works outside of browsers.
• Roll AES128 key aggressively
• Use RSA 4096 peer/dtls certs instead of 2048 - easy to do, doesn't improve the aes issue :(
  • https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/generateCertificate_static
  • https://developer.mozilla.org/en-US/docs/Web/API/RsaHashedKeyGenParams
• Video block scrambling
• Media stream transforms - likely limited browser support
  • https://developer.mozilla.org/en-US/docs/Web/API/RTCRtpSender/transform
• direct data channel management
  • ordered: false - ordered
  • maxRetransmits: 0 - maxRetransmits
  • maxPacketLifeTime: 30 - maxPacketLifeTime
  • custom media codec negotiation (maybe we can use existing codec meta data?)