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.