List open source means to prevent WebRTC leaks in Chrome. #367

2017-11-26T14:32:57Z

aghorler commented

2017-11-26 14:32:57 +00:00

(Migrated from github.com)

Description

Although it's not possible to disable WebRTC in Chrome, an API exists to change its routing settings.

The API can be used to prevent leaks using extensions.

index.html currently mentions that only a single extension exists, and that it can be easily circumvented.

This is no longer true.

The old extension (which has been removed by its developer) attempted to block WebRTC by injecting JavaScript into web pages (a content script). This solution is flawed because it's not possible to inject code into a sandboxed iframe.

Current extensions use an API provided by Chrome, and cannot be circumvented.

HTML Preview

https://htmlpreview.github.io/?https://github.com/aghorler/privacytools.io/blob/master/index.html

### Description Although it's not possible to disable WebRTC in Chrome, an API exists to change its routing settings. The API can be used to prevent leaks using extensions. *index.html* currently mentions that only a single extension exists, and that it can be easily circumvented. This is no longer true. The old extension (which has been removed by its developer) attempted to block WebRTC by injecting JavaScript into web pages (a content script). This solution is flawed because it's not possible to inject code into a sandboxed iframe. Current extensions use an API provided by Chrome, and cannot be circumvented. ### HTML Preview https://htmlpreview.github.io/?https://github.com/aghorler/privacytools.io/blob/master/index.html

ghost commented

2017-11-26 15:03:32 +00:00

(Migrated from github.com)

Thanks

This repo is archived. You cannot comment on pull requests.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#367