- Anatomy of a WebRTC SDP
- YouTube Does WebRTC – Here’s How
- AIY Vision Kit Part 1: TensorFlow Computer Vision on a Raspberry Pi Zero
- Progressive Web Apps (PWA) for WebRTC (Trond Kjetil Bremnes)
- Computer Vision on the Web with WebRTC and TensorFlow
- Reeling in Safari on WebRTC – A Closer Look at What’s Supported
- An Intro to WebRTC’s NAT/Firewall Problem
webrtcH4cKS: ~ So your VPN is leaking because of Chrome’s WebRTC…
Brussel’s Mannneken Pis. Original photo by Flickr user Francisco Antunes (CC BY 2.0)
We have covered the “WebRTC is leaking your IP address” topic a few times, like when I reported what the NY Times was doing and in my WebRTC-Notifier. Periodically this topic comes up now and again in the blogosphere, generally with great shock and horror. This happened again recently, so here is an updated look into this alleged issue.
The recent blog post titled VPN Leak by voidsec highlighting how 19 out of more than 100 VPN services tested “leak” IP addresses via WebRTC is a quite interesting read. Some of the details about WebRTC are not quite correct the results are interesting nonetheless. At is core this is someone who sat down to test a long list of services and their behaviour, one by one. This is not the most exciting research task, but exhaustive studies like this often find something interesting.
