Bromite: Fix WebRTC leakage of private information

Created on 25 Oct 2017  ·  3Comments  ·  Source: bromite/bromite

Chromium v63 breaks build when webRTC is disabled; to get going, I will build it but disable it by default as explained here: https://github.com/copperhead/bugtracker/issues/521

WebRTC needs to be disabled because of leakage of network address and UUIDs, as an user reported on XDA forums.

See also: https://browserleaks.com/webrtc

bug
Source
picture csagan5

Most helpful comment

Fixed in upcoming 63.0.3239.122 by completely disabling webRTC.

picture csagan5 on 27 Dec 2017
👍2

All 3 comments

This seems very resilient; even with this patch 83e140c4f6c76c773f4233ed80d1cb974fda95c5, still there...

csagan5 picture csagan5 on 27 Oct 2017

The solution could be to always return false for those options, since they could be read from the stored configuration (and thus not using the defaults specified in the patch).

Experimenting now with completely disabled WebRTC build.

csagan5 picture csagan5 on 24 Dec 2017

Fixed in upcoming 63.0.3239.122 by completely disabling webRTC.

csagan5 picture csagan5 on 27 Dec 2017
👍2
Was this page helpful?
0 / 5 - 0 ratings

Related issues

Lucaas87 picture Lucaas87  ·  4Comments
leedoyle picture leedoyle  ·  6Comments
darylrobert picture darylrobert  ·  5Comments
elcste picture elcste  ·  5Comments
projectextremum picture projectextremum  ·  6Comments