News for hackers. Stuff that matters.
Re:Google will block local extensions in Chrome 33 for Windows by higherpurpose on Thursday February 13, 2014 @10:44AM (#7231898)
Why is this needed? Wasn't the move to only install local extensions by dragging and dropping on the extensions tab enough to prevent the vast majority of "installing infected extensions by mistake"? What security advantage does having to check a box for Developer Mode on the extension page offer over how it's done now, other than making it slightly harder and more confusing for the user himself to install local extensions?

Google is just one step away from making me quit using Chrome. If they ban external extensions for good with a future Chrome release, that's it, I'm done. I'll start using either Firefox or Opera, and then convince everyone I know to use them, too, just like I did before with Chrome.

Re:Google will block local extensions in Chrome 33 for Windows by royprins on Thursday February 13, 2014 @11:10AM (#7232084)
The advantage should be more in user experience, since this would essentially put a halt to bundled crapware.

People who are willing to move to "Developer mode" will not be the people who will be confused in any way.

Re:Google will block local extensions in Chrome 33 for Windows by higherpurpose on Thursday February 13, 2014 @11:30AM (#7232223)
And how were people confused into dragging and dropping the extensions on the extension page before? That's what I'm saying. I see no security benefit over how it already works.
Re:Google will block local extensions in Chrome 33 for Windows by randomfool on Thursday February 13, 2014 @11:14AM (#7232114)
Local applications can modify Chrome's settings and inject their own extensions with no involvement by the user. This change is targeted at preventing extensions that the user did not explicitly install.