Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Chrome & Chromium
Chrome Extension Manifest V3 May Break uBlock Origin Content Blocker
Message
<blockquote data-quote="CyberTech" data-source="post: 793714" data-attributes="member: 67474"><p>The Google Chrome development team is working on making some changes to the Chrome Extensions platform that would end the functionality of ad-blockers like uBlock Origin and uMatrix, if implemented as defined in the current draft document.</p><p></p><p>Extension capabilities are restricted through a mechanism called <a href="https://developer.chrome.com/extensions/manifestVersion" target="_blank">extension manifest</a>, currently at version 2. In the next revision, Google plans to limit the blocking capabilities of the webRequest API, which these extensions utilize.</p><p></p><p><span style="font-size: 22px"><strong>Breaking content filtering functionality</strong></span></p><p>"In Manifest V3, we will strive to limit the blocking version of webRequest, potentially removing blocking options from most events (making them observational only). Content blockers should instead use declarativeNetRequest," reads the <a href="https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit#heading=h.n3yi078k4z3o" target="_blank">provisional document</a>.</p><p></p><p>This modification would not cover all use cases and the webRequest functionality may end up being preserved in some form, the document states.</p><p></p><p>Developer Raymond Hill says that phasing out 'webRequest' API in favor of the 'declarativeNetRequest' API would mean the death of <a href="https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm" target="_blank">uBlock Origin</a>, his highly popular extension for filtering web content, used by over 10 million users.</p><p></p><p><img src="https://www.bleepstatic.com/images/news/u/1100723/uBlockOrigin-content-blocker.png" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p><p></p><p><a href="https://chrome.google.com/webstore/detail/umatrix/ogfcmafjalglgifnmanfmnieipoejdcf" target="_blank">uMatrix</a>, his other extension that enables the user to define which class of requests made by the web browser should be blocked, would share the same fate.</p><p></p><p><img src="https://www.bleepstatic.com/images/news/u/1100723/uMatrix-content-blocker.png" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p><p></p><p></p><p>"If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin ("uBO") and uMatrix, can no longer exist," he says on the <a href="https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23" target="_blank">bug tracking page for Manifest v3</a>.</p><p></p><p>One argument in favor of the declarativeNetRequest as the primary content-blocking API in extensions is that it performs better. Another is that it offers better privacy guarantees because it allows extensions to tell Chrome what to do with a given request rather than have the browser forward the request to the extension; this way, the extension does not have access to the network details.</p><p></p><p><span style="font-size: 22px"><strong>Filtering limitations</strong></span></p><p>Hill explains that his extensions are incompatible with the proposed declarativeNetRequest API because it allows only one specific filtering engine, whereas uBlock Origin and uMatrix rely on various filtering designs to do their job properly.</p><p></p><p>The proposed modification would promote static filtering capabilities that are compatible with AdBlock Plus and would limit the number of filters to 30,000.</p><p></p><p>Hill gives the example of the <a href="https://easylist.to/" target="_blank">EasyList filters</a> with rules for removing unwanted web content, which is larger than 30,000 entries and is not sufficient for a modern user's filtering needs.</p><p></p><p>The rule set is used by AdBlock Plus and uBlock Origin and it is much larger than the limit imposed by the 'declarativeNetRequest'.</p><p></p><p>Hill's comments remained unaddressed by the developers, but they got the vote of Chrome users chiming in. Some of them say that they would switch to a different browser should the proposal make it as it is into the final version of the manifest.</p><p></p><p>However, discussions are ongoing and the draft document for manifest version 3 states that declarativeNetRequest would act as the primary content-blocking API in extensions. This suggests that secondary methods may be available.</p><p></p><p></p><p>Source: <a href="https://www.bleepingcomputer.com/news/security/chrome-extension-manifest-v3-may-break-ublock-origin-content-blocker/" target="_blank">Chrome Extension Manifest V3 May Break uBlock Origin Content Blocker</a></p></blockquote><p></p>
[QUOTE="CyberTech, post: 793714, member: 67474"] The Google Chrome development team is working on making some changes to the Chrome Extensions platform that would end the functionality of ad-blockers like uBlock Origin and uMatrix, if implemented as defined in the current draft document. Extension capabilities are restricted through a mechanism called [URL='https://developer.chrome.com/extensions/manifestVersion']extension manifest[/URL], currently at version 2. In the next revision, Google plans to limit the blocking capabilities of the webRequest API, which these extensions utilize. [SIZE=22px][B]Breaking content filtering functionality[/B][/SIZE] "In Manifest V3, we will strive to limit the blocking version of webRequest, potentially removing blocking options from most events (making them observational only). Content blockers should instead use declarativeNetRequest," reads the [URL='https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit#heading=h.n3yi078k4z3o']provisional document[/URL]. This modification would not cover all use cases and the webRequest functionality may end up being preserved in some form, the document states. Developer Raymond Hill says that phasing out 'webRequest' API in favor of the 'declarativeNetRequest' API would mean the death of [URL='https://chrome.google.com/webstore/detail/ublock-origin/cjpalhdlnbpafiamejdnhcphjbkeiagm']uBlock Origin[/URL], his highly popular extension for filtering web content, used by over 10 million users. [IMG]https://www.bleepstatic.com/images/news/u/1100723/uBlockOrigin-content-blocker.png[/IMG] [URL='https://chrome.google.com/webstore/detail/umatrix/ogfcmafjalglgifnmanfmnieipoejdcf']uMatrix[/URL], his other extension that enables the user to define which class of requests made by the web browser should be blocked, would share the same fate. [IMG]https://www.bleepstatic.com/images/news/u/1100723/uMatrix-content-blocker.png[/IMG] "If this (quite limited) declarativeNetRequest API ends up being the only way content blockers can accomplish their duty, this essentially means that two content blockers I have maintained for years, uBlock Origin ("uBO") and uMatrix, can no longer exist," he says on the [URL='https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23']bug tracking page for Manifest v3[/URL]. One argument in favor of the declarativeNetRequest as the primary content-blocking API in extensions is that it performs better. Another is that it offers better privacy guarantees because it allows extensions to tell Chrome what to do with a given request rather than have the browser forward the request to the extension; this way, the extension does not have access to the network details. [SIZE=22px][B]Filtering limitations[/B][/SIZE] Hill explains that his extensions are incompatible with the proposed declarativeNetRequest API because it allows only one specific filtering engine, whereas uBlock Origin and uMatrix rely on various filtering designs to do their job properly. The proposed modification would promote static filtering capabilities that are compatible with AdBlock Plus and would limit the number of filters to 30,000. Hill gives the example of the [URL='https://easylist.to/']EasyList filters[/URL] with rules for removing unwanted web content, which is larger than 30,000 entries and is not sufficient for a modern user's filtering needs. The rule set is used by AdBlock Plus and uBlock Origin and it is much larger than the limit imposed by the 'declarativeNetRequest'. Hill's comments remained unaddressed by the developers, but they got the vote of Chrome users chiming in. Some of them say that they would switch to a different browser should the proposal make it as it is into the final version of the manifest. However, discussions are ongoing and the draft document for manifest version 3 states that declarativeNetRequest would act as the primary content-blocking API in extensions. This suggests that secondary methods may be available. Source: [URL="https://www.bleepingcomputer.com/news/security/chrome-extension-manifest-v3-may-break-ublock-origin-content-blocker/"]Chrome Extension Manifest V3 May Break uBlock Origin Content Blocker[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
