Google snuck surveillance code into Chromium?
How did I miss this in June... http://arstechnica.com/security/2015/06/not-ok-google-chromium-voice-extension-pulled-after-spying-concerns/
And to Chromium, not Chrome...
I use Chromium as a secondary browser, mostly as a sandbox for Google/Facebook applications. But sometimes I get lazy and start doing a lot more browsing in Chromium if I don't have IceWeasel open. This radically changes my feeling of Chromium...
juancuyo, juancuyo, mray INACTIVE, jrobertson and 2 others shared this.
I don't think this was the way the process is supposed to work. Google sneaking something nasty into the free software version that's intended for the proprietary version, and it being discovered through the Debian bug reporting process after it's already been pushed into "production" on user's computers?
This radically changes my perspective on how Google views Chromium. While I'm not necessarily concerned about this specific problem, I'm very concerned about what this says about Google's practices with Chromium development.
Blaise Alleyne at 2015-10-28T02:28:01Z
jrobertson, Stephen Sekula likes this.