WebRTC, Or How Secure Is P2P Browser Communication? [BAD AUDIO]
summary
Examines the security of WebRTC peer-to-peer communication in browsers, focusing on technologies like WebRTC APIs, signaling, and the browser’s handling of P2P connections. Covers threats and vulnerabilities specific to P2P browser setups and evaluates the mechanisms browsers use to protect or expose data during WebRTC sessions.
AI-written summary · about
chapters (28)
- 0:00WebRTC, Or How Secure Is P2P Browser Communication?
- 0:40About us: Martin Johns
- 1:30Overview
- 2:05Audio/video communication ... in the browser
- 3:20WebRTC architecture (Simplified)
- 4:56Various WebRTC deployments
- 6:08Multiple peer topologies
- 7:08Signaling path
- 8:51Setting up the media path
- 9:40SDP: Session description protocol • Initialization parameters for streaming media
- 10:48UDP hole punching
- 11:30When to use STUN/TURN/ICE?
- 12:39WebRTC architecture (less simplified)
- 13:04Identity provision
- 14:11WebRTC architecture (full)
- 15:04Fully JavaScript empowered...
- 18:37Handling ICE Candidates
- 19:06Capturing a video stream
- 21:56Increased attack surface
- 23:31Permission model / UI feedback
- 28:42Meta-data leakage: Trace that communication has happened
- 30:57Leaking local network info (CE)
- 33:29DTLS-RSTP to the rescue
- 35:35Eavesdropping on the connection
- 36:46Setting up the media channel with the IdP
- 38:41IDP setups
- 40:59Take home message
- 44:44Relevant sources
related talks
33mWebRTC Change Communications Forever
27mWebRTC: Real-Time Communications
10mWebRTC - future of Video Chats
31mWebRTC: Real-time communication without plugins
20mSharing is Caring: build a peer-to-peer network with WebRTC
46mWebRTC: Let’s Revolutionize Information Sharing in the Browser
33mWebRTC Change Communcations Forever
53mThe State of WebRTC