Google embeds proprietary code in free (?) Chromium

I did not see about this article on Habré and decided to write.

In general, Google’s policies are sometimes astounding. “Chromium” with version 43 without the user's knowledge installs the hotword extension (the web directory module that contains the NaCl binary module), which is immediately downloaded for the convenience of the user, as Google says.

One of the users accidentally stumbled upon this and opened a bug. With this, in fact, it all started. The extension has access to the microphone and works with the OK, Google service. It does not appear in the list of extensions, which is accessible to a simple user, because, as I quote Google, "is a component-extension". Which also means that if you still manage to display it with the other extensions, the components from Google that are part of Chromium (this can be done using the command line flag --show-component-extension-options), then it cannot be deleted, since it It is a "controlled» ( 'managed ) extension. However, it is stored in the folder with the other Chromium extensions in the subfolder / lccekmodgklaepjeofjdjpbminllajkg /

Theoretically, Google reassures, since Chromium is an open source browser, you can verify that it does not launch extensions until you check the box (about “OK, Google”) in the search box in the settings, although it downloads it . Debian has already added a patch that adds the enable_hotwording flag, which is turned off by default. You can check the status of your Hotword on the chrome: // voicesearch page. Google does not see a problem ... Good luck in removing the extension, and may Open Source come with you!


In general, it is very interesting to hear your opinion on this issue, how you are struggling with the problem, are you still using Chromium (because it is very convenient or for some other reasons).

The original discussion can be read in English at: code.google.com/p/chromium/issues/detail?id=500922

Does this change your attitude towards Chromium?

UPD 1: Since the article was in the sandbox, it could not be polled, but now I decided to add it.

UPD 2: Chromium developers turned off the automatic installation of a proprietary add-on (June 23). Fortunately, Google listened to the discontented community :)