Forum Moderators: goodroi
Google Hotwording, Chrome Now Has Audio Spy Payload
Hotwording downloads a shared module from the web store containing a NaCl module. There is a desire to build and distribute Chromium without this happening. This change adds an "enable_hotwording" build flag that is enabled by default, but can be disabled at compile time.
To disable hotwording, pass "enable_hotwording=0" in your GYP_DEFINES, or "enable_hotwording = false" in your GN config. This will prevent the shared module from being downloaded, and also prevent the option from showing up in settings.
Where is the recorded material stored, and for how long?
Are we talking about "Yuk, they shouldn't be doing that" or about "Vast potential for abuse"?
New Chromium builds will no longer download/install the Hotword Shared Module and will automatically remove the module on startup if it was previously installed.
A closed-source and binary-only kernel module caused a fair fuss when it was found inveigling its way into the very much open-source Chromium.
Thanking the community for their attention and input on the issue, one of the project developers told the issues ticket thread that "as of the newly-landed r335874, Chromium builds, by default, will not download this module at all."