WebRTC , Privacy Badger and VPN, is this a concern?

I sometimes check my VPN security at httxx://ipleak.net/ I notice if I turn off Privacy badger the site detects WebRTC. I have no clue of the IP addresses it displays, except the one that starts with 192.168... it is a media device connected to that in my internal network. But that seems sometimes change to for example
10.103.118.138 but it doesnt show my ISP IP.
Do I have to worry if I dont use Privacy badger?
I have tried with three different VPN providers: NordVPN, Anonine and Kaspersky Secure Connection.

 

I use the Disable WebRTC add-on in Firefox.

 

Correct me if I'm wrong, but you don't need to entirely disable WebRTC.

uBlock Origin is one example which has an option "Prevent WebRTC from leaking local IP address" but as far as I know, WebRTC still works.

 

I have no use for WebRTC, so hey

 

Privacy Badger has a "Prevent WebRTC from leaking local IP address" feature.

 

use CentBrowser,
https://www.centbrowser.com

 

I only see that setting in the Chrome version, but not in Firefox. Running current versions of both.

 

A good WebRTC leak test is available on https://browserleaks.com/

Scroll down to the bottom of the main page for the link under "More Tools".

 

Today, I started using the WebRTC Leak Prevent extension in Chrome as, like mirimir, I don't need RTC.

JPC

 

Does it only prevent IP leak by WebRTC, or does it block WebRTC entirely?

 

It does prevent the leaking

Selectable options:

 

Thnx for answer.

On reviews page author says this:



So IDK if it adds anything to WebRTC block that is included in uBlock Origin.

 

Not possible to block WebRTC in Chrome?

 

It seems that not entirely only some aspects or usage cases.
Interesting there is a flag for Chrome on Android which can disable it entirely

 

I just can't bring myself to use Chrome.

 

= ScriptSafe

 

Or the user can use a "No WebRTC"-release of Chromium

 

OK, thanks

 

You can already prevent leaks using an extension like uBO, as has been repeated several times in this thread.

You do not need a special build of Chrome to accomplish this, so the reasoning of creating that to "prevent IP address leaks" is idiotic.

If you want to create a special build to completely remove all support for WebRTC, sure, but do not give the excuse that you built it for preventing leaks, that's a lie. You do not need a custom build to do that.

However it does take a special kind of paranoid person to trust a random nobody to create a WebRTC-free version of Chrome versus using Chrome with a popular extension like uBO.