
Extensive security and hardening fixes across the core decoder/encoder, box buffers, and plugins (EXR, GIF, APNG/PNG, PAM/PNM/PGX). This includes fixes for integer overflows/underflows, out-of-bounds reads/writes, buffer overflows, and null pointer guards
Oh damn I didn’t know about that, for sure then.
score 1 · canonical
I don’t consider this an upside,
webRequestallows significantly more flexible code (and by extensions more techniques to defeat anti-adblock) than the rulesets made for specifically content blocking extensions do. The only thing this does is ossify content block capability.This is moot because I don’t think any mortal user is informed adequately enough to give consent for extension permissions. If you give any permission, you’re extending trust to the extension author to not abuse it. Authors don’t even have to give you inline justification for why any specific permission is required.
Mozilla realized this problem and reviews extensions that go through the extension store before signing it, I have my gripes with the system but it’s what we’re left with.
Whatever transgressions done, the current status quo is significantly better than whatever ABP and friends are doing with “”“acceptable ads”“”.
It’s also going to be significantly better than trusting yet another Chromium fork to patch in an engine per patchfiles, which is my argument :/
score 1 · canonical