UBlock origin has some web_accessible_resources that it requires to be accessible to all origins, but it attempts to prevent them from being read via a network listener that blocks the request unless it contains a "secret token". This is superior for security, as it prevents an arbitrary site from easily being able to enumerate your extensions. However, in the recently introduced manifest v3, a developer can specify which hosts are allowed to read the assets. Which, by the way, almost every major extension has a few. You could hypothetically fingerprint users by scanning for the presence of all every extension with web_accessible_resources. This means any extension with web_accessible_resources can be detected by a webpage. In manifest v2, these assets are available to any webpage. These assets then become available via the chrome-extension:// URI, e.g. These assets are listed in the extension's manifest.json file under the web_accessible_resources key. uBO Lite (uBOL), an experimental permission-less MV3 API-based content blocker.I recently found a neat trick to check for the presence of Chrome extensions in a user's browser.Ĭhrome extensions often need to expose files to webpages (images, fonts, etc.) to webpages. No broad host permissions at install time - extended permissions are granted explicitly by the user on a per-site basis.Įntirely declarative for reliability and CPU/memory efficiency. Keep in mind this is still a work in progress, with these end goals: You can add more rulesets by visiting the options page - click the Cogs icon in the popup panel. Peter Lowe’s Ad and tracking server list.The default ruleset corresponds to at least uBlock Origin's default filterset: If you pick the Optimal or Complete mode as the default one, you will need to grant uBOL the permission to modify and read data on all websites: You can set the default filtering mode from uBOL's options page. If you accept uBOL's request for additional permissions on the current site, it will be able to better filter content for the current site: The browser will then warn you about the effects of granting the additional permissions requested by the extension on the current site, and you will have to tell the browser whether you accept or decline the request: To grant extended permissions on a given site, open the popup panel and pick a higher filtering mode such as Optimal or Complete. UBOL allows you to explicitly grant extended permissions on specific sites of your choice so that it can better filter on those sites using declarative cosmetic and scriptlet injections. UBOL does not require broad "read/modify data" permission at install time, hence its limited capabilities out of the box compared to uBlock Origin or other content blockers requiring broad "read/modify data" permissions at install time. This means that uBOL itself does not consume CPU/memory resources while content blocking is ongoing - uBOL's service worker process is required only when you interact with the popup panel or the option pages. UBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension. The uBlock Origin extension remains an industry leading, open-source, cross-platform browser extension with software developed specifically for multiple platform use, and as of 2024, uBlock Origin’s extension is available for several of the most widely used browsers, including: Chrome, Chromium, Edge, Opera, Firefox and all Safari releases prio. UBO Lite (uBOL), an experimental permission-less MV3 API-based content blocker. There is a uBlock Origin Lite that is unofficially announced in the GitHub for uBO: Description Meanwhile, if you want to try it, you can install it from Chrome WebStore. We will talk about each of them in detail. While developing the prototype, we faced a lot of serious problems caused by the features of the new API: some of them we managed to overcome, and some we had to reconcile with. But we coped with it, of course, and proved that ad blockers will survive even after the apocalypse that is Manifest V3. The task was not an easy one: the new API was still raw, some aspects were being finalized and did not work as intended. In mid-2021, we started working on the prototype of a new extension that would be able to block ads even within the strict limits of Manifest V3. AdGuard that I use on my Android device has already claimed they are fine with v3 Manifest: AdGuard publishes the world's first ad blocker built on Manifest V3
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |