Preventing real IP address leakage over WebRTC

WebRTC is an API definition that supports browser-to-browser applications for voice calling, video chat, and P2P file sharing. It's enabled by default in Firefox and Chrome. It could be a reason of real IP address leakage.

At https://diafygi.github.io/webrtc-ips/ it's available to know the public IP addresses that are able to got over WebRTC.

Firefox

Manually
  • Enter "about:config" in the address bar
  • Press the button "I'll be careful, I promise!"
  • Search for "media.peerconnection.enabled"
  • Double click the entry to set the column "Value" to "false"
With add-ons

Use WebRTC-Button to activate/deactivate WebRTC support with a simple button. Or uBlock Origin with the checked option "Prevent WebRTC from leaking local IP addresses".

With add-ons for advanced users

Advanced users can use NoScript (requires technical knowledge to configure) or Policeman add-ons to create rules based on domain name, type of element and type of resource being requested.

Chrome on Android

  • Enter "chrome://flags/#disable-webrtc" in the address bar
  • Press "Enable"
  • Terminate application or make a reboot for the device

Chrome on Desktop

At this time there is no way to disable WebRTC support in Chrome totally. But with WebRTC Leak Prevent extension (Chrome version 42+) it's available to disable WebRTC Multiple Routes, that helps to use only default gateway for connections. Also uBlock Origin extension can be used and it's option "Prevent WebRTC from leaking local IP addresses" for doing the same thing.

Advanced users also can use Script Safe (like NoScript for Firefox) to block unwanted elements (like scripts, frames and etc.) for preventing IP address leakage.

Remember that full disabling WebRTC support may break some web services' functionality (e.g. video and audio chats).


show comments