List open source means to prevent WebRTC leaks in Chrome. #367
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#367
Loading…
Reference in New Issue
No description provided.
Delete Branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Thanks