3 ms·
Ah, thank you. So the idea here is that extensions will still have the read access to requests, which is all attackers care about (typically). Confirmation woul
by insanitybit 3y ago
Ah, thank you. So the idea here is that extensions will still have the read access to requests, which is all attackers care about (typically). Confirmation would be interesting - at minimum I thought that inspecting requests (read only) Was being limited, but I'm just a casual observer.
- Vinnl 3y agoI think this is the relevant API: https://developer.chrome.com/docs/extensions/reference/webRequest/ https://developer.chrome.com/docs/extensions/reference/webRe... > As of Manifest V3, the "webRequestBlocking" permission is no longer available for most extensions. Consider "declarativeNetRequest", which enables use of the declarativeNetRequest API. Aside from "webRequestBlocking", the webRequest API will be unchanged and available for normal use. So the other functionality, to inspect web requests, will still be available.