Hacker News Reader

Which is why chrome is moving toward a policy of only allowing web store extensions, end of story.

It sucks, and nobody is happy with it, but at the end of the day it's the only thing that seems to be working.

I expect to see these same companies try ever more fragile and bad methods to bypass these restrictions. If chrome refuses to load extensions from disk, they'll inject themselves into the process address space somewhere, which as a bonus will likely introduce sandbox escape vulnerabilities. This is what the AV vendors are doing these days.

They already try to do that. Hell some have even gone as far as to remove chrome, and install their own "infected" chromium compiled with their extension whitelisted and updates disabled.

It's terrifying. And while you could make a case for this "not being chrome's problem", the fact is that it's really hurting their user base, so they can't not do something about it.

AIUI, many of the top crashes of Chrome are from code injected into the address space (or rewriting the binary on disk). So yeah, it is hurting their user base and as a result it is hurting them.

Reply on news.ycombinator.com