Thursday, November 7, 2013

Google to ban Chrome extensions for Windows hosted outside its Web Store

Google to ban Chrome extensions for Windows hosted outside its Web Store

Google to ban Chrome extensions for Windows hosted outside its Web Store

There will only be one place for Chrome browser extensions to be stored in 2014, as Google is about to require all extensions to be hosted on the Chrome Web Store.

This isn't another Google-Microsoft app tiff. Malicious extensions are the reason developers are being forced to migrate all of their extensions Google's internal servers starting in January.

"Many services bundle useful companion extensions, which causes Chrome to ask whether you want to install them (or not)," explained Erik Kay, Google Engineering Director, i n an official blog post today.

"However, bad actors have abused this mechanism, bypassing the prompt to silently install malicious extensions that override browser settings and alter the user experience in undesired ways."

One example given that Google highlighted involved replacing the New Tab Page without users' approval. The company even linked to hundreds of complaints from Windows users to back up this reasoning.

You shouldn't see a difference

Chrome users shouldn't see much of a change due to the new security efforts announced today.

"There will be no impact to your users, who will still be able to use your extension as if nothing changed," Google advised developers.

He also mentioned that developers who want to keep extensions hidden from the Web Store can do so, in case they're used internally and shouldn't be shared with the public.

The only difference end-users will see is if developers don't migrate over to being hosted on the Chrome Web Store right away.

"If your extensions are currently hosted outside the Chrome Web Store you should migrate them as soon as possible," he warned.

Protecting our users is a key priority, and we believe this change will help those whose browser has been compromised by unwanted extensions.


    






No comments:

Post a Comment

//PART 2