-
Notifications
You must be signed in to change notification settings - Fork 598
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.
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
Bypass naive WebRTC blocking #8
Conversation
Ping? |
Sorry for the delay, I wanted to reach out to the WebRTC Block developers and give them a few days to update their extension. However, I have not heard back, so I will merge this pull request. Thanks! |
Actually, I don't think it is possible to fix this problem in a Chrome extension. |
It appears to me that rebuilding chromium with |
@upsuper should be possible by adding
to the content_scripts section in the extension manifest. That way, the content script is executed on about:blank iframes as well. |
@fippo I don't think so. I don't think the browser should run any other script when one piece of script is running. |
@upsuper take the webrtcblock source from chromes extension directory, modify the manifest.json as indicated, import it as your own extension. breaks the (awesome) iframe hack for me. |
@fippo then I just need to specify |
@diafygi you probably could also add the code I just mentioned above to the detection script. |
Pull request please? Please update both the |
OK, I'll do it later. It seems I can't change two files in one commit on Github directly. |
@upsuper On newest versions of Chrome "content_scripts": [ {
"all_frames": true,
"match_about_blank": true, in manifest.json is really break this webrtc-ips, tested on latest Chromium LKGR build for Win: #9662 P.S. Also you can modify "matches": [ "http://*/*", "https://*/*" ], to "matches": [ "http://*/*", "https://*/*", "file://*/*" ], for a quick local check / for blocking from local host(s) files too. |
This can bypass the Chrome extension "WebRTC Block".