News for hackers. Stuff that matters.
Re:Google sets burial date for legacy Chrome Extensions, fea... by dobladov on Tuesday September 28, 2021 @03:26AM (#28680199)
Is v3 an horrible solution or the deprecation of v2 in 2023?

I ported one of my extensions to v3 and while the process was not completely trivial it did not took more than a few hours, in my opinion the change is worth it this makes extensions more secure.

As far as I know Firefox is also moving to v3, maybe not enforcing it for now, but they will probably deprecate v2 at some point.

Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @03:57AM (#28680332)
The new declarative APIs are great. They will protect user data from potentially malicious extensions.

The thing is uBlock Origin is just so important and trusted that these restrictions shouldn't apply to it. The functionality of uBlock Origin is just so fundamental and unambiguously pro-user it should be integrated into the browsers themselves. Conflicts of interest prevent that unfortunately but the fact remains that browsers without uBlock Origin installed cannot call themselves user agents.

uBlock Origin should just get access to everything so it can do its job as well as it possibly can. For everyone else, there's the standard APIs.

Re:Google sets burial date for legacy Chrome Extensions, fea... by mmis1000 on Tuesday September 28, 2021 @04:30AM (#28680494)
> They will protect user data from potentially malicious extensions.

No, they won't. You can still log requests however you want. The only difference is you can't modify/stop it. So the privacy concern is pure BS.

Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @07:17AM (#28681443)
How so? From what I've read, the whole point of the declarative API is to tell the browser what you want done so that it can do it without letting the extension actually touch any data.

If this doesn't work, then there's no point to the new API.

Re:Google sets burial date for legacy Chrome Extensions, fea... by mmis1000 on Tuesday September 28, 2021 @08:40AM (#28682056)
That's why it is pure bs at first place.

The webrequest api didn't got removed completely, only the part for modify/block request.

Only ad blockers will stole your data and others that logs them however they want will log them nicely? What world are Google's team lives in? Are we even on the same time line?

Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @09:47AM (#28682736)
I see. I agree, that's pure bullshit. Google's intentions are transparent.

Can you confirm the new declarative APIs work as intended? Maybe they do restrict extensions. I agree that it's pointless if they don't remove the older APIs.

Re:Google sets burial date for legacy Chrome Extensions, fea... by BoxOfRain on Tuesday September 28, 2021 @04:28AM (#28680486)
Google is first and foremost an advertising company, it's in their interest to hobble ad blockers as much as possible. Personally I'm hoping that they do, because it'll drive people away from Chrome and nip what's looking increasingly like a monopoly in the bud by driving users to browsers that do support ad blocking.
Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @07:22AM (#28681493)
> it'll drive people away from Chrome and nip what's looking increasingly like a monopoly in the bud by driving users to browsers that do support ad blocking

I certainly hope so. I showed Firefox and uBlock Origin to all my friends and they loved it, especially the fact it blocks YouTube ads. Lots of people simply don't know about this.

Re:Google sets burial date for legacy Chrome Extensions, fea... by BoxOfRain on Tuesday September 28, 2021 @09:34AM (#28682587)
Yeah, I don't really do "tech support" for family members any more because I've not used Windows in such a long time I'm pretty useless at troubleshooting it, but I do take the time to install Firefox and ad blockers on it which is worthwhile even if you don't have an issue with the adtech industry because it reduces the attack surface for malware.
Re:Google sets burial date for legacy Chrome Extensions, fea... by matheusmoreira on Tuesday September 28, 2021 @09:56AM (#28682817)
Similar experiences here. I don't know anything about Windows anymore but I'll still install Firerox with uBlock Origin on every computer I come across. People notice that the web is just so much nicer. Most don't understand why, they just know. Malware also stopped being an issue: no more malicious ads for them to click.
Re:Google sets burial date for legacy Chrome Extensions, fea... by input_sh on Tuesday September 28, 2021 @03:42AM (#28680283)
While they're interested in maintaining compatibility with Chrome's v3, there's no standard that forces them to make every single v3 change Chrome does.

v2 also already differs in some ways in which Firefox thinks it makes sense. I'm not scared at all that they're gonna deprecate webRequest.BlockingResponse in favour of declarativeNetRequest, which is the specific API function that adblockers rely on. After all, that function has nothing to do with security, best you could argue is that it's related to performance due to filter lists becoming absurdly long.

Re:Google sets burial date for legacy Chrome Extensions, fea... by dotancohen on Tuesday September 28, 2021 @04:00AM (#28680352)
In the context of `webRequest.BlockingResponse` being a performance bottleneck due to filter lists becoming absurdly long, it does in fact become a security issue.

Filter lists are as long as they are because that is the amount of domains that have demonstrated an interest in harming our security (and for many people, online privacy _is_ physical security). Filterlists are blacklists, not whitelists, so they only grow when well-known entities play foul.

Re:Google sets burial date for legacy Chrome Extensions, fea... by kevingadd on Tuesday September 28, 2021 @03:34AM (#28680236)
An extension API that can't implement ad-blockers properly is an extension API that is broken by design. So yes, it's a horrible solution.
Re:Google sets burial date for legacy Chrome Extensions, fea... by selcuka on Tuesday September 28, 2021 @03:42AM (#28680288)
It's not only a simple Manifest version change. They have also deprecated the webRequest API, which is essential to implement any type of content filter or an ad blocker.