Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

investigate webRequest bypasses #6997

Closed
diracdeltas opened this issue Feb 2, 2017 · 0 comments
Closed

investigate webRequest bypasses #6997

diracdeltas opened this issue Feb 2, 2017 · 0 comments

Comments

@diracdeltas
Copy link
Member

related: #6831 #6843

currently ads may be able to bypass Brave's builtin blocking by being excluded from webRequest interception. i suspect websockets is the major one, based on https://bugs.chromium.org/p/chromium/issues/detail?id=129353.

we should also ignore https://cs.chromium.org/chromium/src/extensions/browser/api/web_request/web_request_permissions.cc?sq=package:chromium&dr=C&l=46 for the Brave extension

@diracdeltas diracdeltas added this to the 0.13.3 milestone Feb 2, 2017
@diracdeltas diracdeltas self-assigned this Feb 2, 2017
diracdeltas added a commit that referenced this issue Feb 8, 2017
Fix #6997.
Note: this works around the issue of websocket requests being associated with tabId -1, which seems wrong and is why websocket URLs do not show up in the Bravery Panel stats.

Auditors: @bridiver

Test Plan: covered by automated test
@bbondy bbondy modified the milestones: 0.13.6, 0.13.5 Feb 16, 2017
diracdeltas added a commit that referenced this issue Feb 16, 2017
Fix #6997.
Requires brave/muon#160

Auditors: @bridiver

Test Plan: covered by automated test
@diracdeltas diracdeltas modified the milestones: 0.13.5, 0.13.6 Feb 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants