Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix WebRTC leakage of private information #9

Closed
csagan5 opened this issue Oct 25, 2017 · 3 comments
Closed

Fix WebRTC leakage of private information #9

csagan5 opened this issue Oct 25, 2017 · 3 comments
Assignees
@csagan5
Labels
bug

Comments

@csagan5
Copy link
Contributor

csagan5 commented Oct 25, 2017

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
@csagan5 csagan5 self-assigned this Oct 25, 2017
@csagan5 csagan5 added the bug label Oct 25, 2017
@csagan5
Copy link
Contributor Author

csagan5 commented Oct 27, 2017

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

@csagan5
Copy link
Contributor Author

csagan5 commented Dec 24, 2017 •
edited

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 csagan5 changed the title Build WebRTC, but disable it by default Fix WebRTC leakage of private information Dec 24, 2017
@csagan5
Copy link
Contributor Author

csagan5 commented Dec 27, 2017

Fixed in upcoming 63.0.3239.122 by completely disabling webRTC.

@csagan5 csagan5 closed this as completed Dec 27, 2017
@norbertc norbertc mentioned this issue Feb 9, 2020
Closed
@khorser khorser mentioned this issue Jun 28, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csagan5 csagan5

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@csagan5