Page 2 of 2

Re: WebRTC Block Extension

Posted: Fri Oct 13, 2017 2:07 pm
by SRWare

The Extension blocks the LEAK of your IP-Address. THAT is the reason why WebRTC can be problematic.
It does not blocks WebRTC in the "core" of the browser - which is worth nothing.

WebRTC Block Extension

Posted: Fri May 11, 2018 6:28 pm
by JustinKnili
Hello all, i did a quickly search about but i did not found nothing about.
Its possible to set up now to block a expecify group or extension to not call outside if is not in working time? like weekends...

Re: WebRTC Block Extension

Posted: Wed Aug 15, 2018 9:38 pm
by BiggieSmalls
Will no longer install on my SRIron version 67.0.3500.0 (Developer Build) (64-bit). It will only offer to save the file. How do I install?

@monstertruckpa I don't see those options on the Adguard extension that I installed. Those check boxes must only exist in the paid version, right?

Never mind. Switched to WebRTC Network Limiter and Java script blocker extensions. Thanks for that website @monstertruckpa.

Re: WebRTC Block Extension

Posted: Tue Dec 03, 2019 10:03 am
by TsutomuTakakura
SRWare wrote:We will soon stop making special WebRTC-Builds and replace it with the functionality of our new extension because we want to make it also available for our Linux and OS X customers and also make it optinal because some poeple want to switch WebRTC on and off depending on their usage.

Download: (for Win, Linux, OS X)

Just install the extension and WebRTC IP Leaks are stopped. Please get sure to allow it also for Incognito!
You want to use WebRTC again for a while? Simply disable the extension temporarily.

What are WebRTC Leaks? ... dress.html



Good offer. I hope many appreciate its need.

Re: WebRTC Block Extension

Posted: Wed Feb 05, 2020 11:14 am
by Maxis
Hi, SRWare! Thanks for a great browser.
Can you please do something with Device-ID in WebRTC? As described there this can be use to tracking users.
First of all, media device enumeration works only in Chromium-based web browsers since Chrome 30 or later.

Device ID's — it's a unique identifiers of an audio/video devices installed in your system. Even if you have no camera/microphone, Chrome may detect more than one device, such as «Line In», «Aux», «CD Player», etc, depending on the system drivers.

Full list of available media devices you can check in «chrome://settings/content ⇒ Media»

Of course, Google Chrome does not allow foreign websites to see the actual Model ID of your hardware devices, instead it provides self-generated hashes. But at the same time, any website is allowed to take this fingerprints without user confirmation.

How persistent and trackable these Device ID's?

Well, for most users this ID's may remain unchanged for months.

WebRTC Device ID is a HMAC of:

Value of the "media":{"device_id_salt"} located in «Chrome\Data\profile\Preferences». Salt generates randomly at the Chrome's first launch. It's renew every time user doing «Clear browsing data ⇒ Cookies and other site and plug-in data». Also, Incognito Mode does not touch «device_id_salt», but generates its own salt for every session.

Origin, aka «protocol://hostname:port». This dependence is not a problem for user tracking, script can be requested from constant host through iframe, and it will be same origin and same Device ID's on any domains.

Raw Device ID of the physical device installed in your system.

So, WebRTC Device Fingerprints persistent to:

Changing ISP, IP address.
Restarting browser, rebooting system.
Clearing cookies and cache through third-party addons like EditThisCookie or CCleaner.
WebRTC Device Fingerprints not persistent to:

Clearing cookies through «chrome://settings/clearBrowserData».
Using new session of Incognito mode.