The problem is, because of their configuration, if you are using Brave Shields, you are not just trusting Brave Shields, you are trusting uBO and all other lists as well. If you don’t trust uBO but still use Brave Shield, it will just give you a false sense of security.
1 Like
This is an interesting POC, per my limited understanding, couldn’t this also apply to uBOL (on optimal mode) ? ofc you don’t have custom lists, but wouldn’t a compromised list on uBOL also achieve the same thing.
It worked in a new profile… Maybe my antivirus was doing this ?
BTW, it isn’t true that extensions don’t need to ask permissions, they do.
Firefox (tested for camera)
This could be said about Google’s phising protection as well… On an indvidual basis, this might make sense, but for thousands of users, some will be impacted by this.
Not to mention that many trackers will not be blocked in time …
Just to be clear, this doesn’t apply to Firefox.
uBO Lite is permissionless, but you can choose to enable optimal mode on a per-site basis.
I was refering to the case if you enable optimal mode in the settings, which require the “Read and modify” permission.
If you grant that permission globally, then there is no point in using uBO Lite.
its time to move to firefox dev edition + arkenfox.
Brave Shields are more than enough for most people. It’s also based on ublock list if I’m not wrong. Also installing extension will make you stand out more than other brave users. Not to mention, that build is currently nightly, and this could be a bug as well. So let’s wait and watch!
This has reportedly been observed in upstream Chrome Canary. Google is finally disabling Mv2 extensions.
According to Google’s Mv2 deprecation timeline :
October 9th 2024: an update on Manifest V2 phase-out.
Over the last few months, we have continued with the Manifest V2 phase-out. Currently the chrome://extensions page displays a warning banner for all users of Manifest V2 extensions. Additionally, we have started disabling Manifest V2 extensions on pre-stable channels.
We will now begin disabling installed extensions still using Manifest V2 in Chrome stable. This change will be slowly rolled out over the following weeks. Users will be directed to the Chrome Web Store, where they will be recommended Manifest V3 alternatives for their disabled extension. For a short time, users will still be able to turn their Manifest V2 extensions back on. Enterprises using the ExtensionManifestV2Availability policy will be exempt from any browser changes until June 2025. See our May 2024 blog for more context.
So they might have inherited this due to an update in upstream chromium project. I hope they update the code to keep allowing the Mv2 extensions a little longer.
But still for adblocking in general, their shields is completely separate from extensions and will work properly as this has been discussed in the past on brave’s official forums.
Please note that my issue has been resolved, so this might not been true.
1 Like
Understood!