On 19/10/14 12:11, Martin Steigerwald wrote: > Am Samstag, 18. Oktober 2014, 19:06:33 schrieb Michael Gilbert: >> control: severity -1 important >> >> On Sat, Oct 18, 2014 at 5:12 AM, Osamu Aoki wrote: >>> At least adding this key fixed my system. (I have removed old >>> ~/.chromium directory before adding the API key. If removal of this is >>> required for upgrade, please consider adding entry to debian/NEWS) >> >> That patch, of course as simple as it is, looks ok, almost. Like I >> said my plan is to put it in a separate chromium-apikeys package. >> >> I'll have time to work on that tomorrow. Those interested can then >> press ftp masters for a quick review. > > Honestly I am starting to wonder… when does Chromium use Google APIs and > exactly *why* do Chromium developers *insist* with a nagging warning to have > API key installed? What user behaviour tracking abilities does it give to > Google? And did I really disable all privacy harming features in it already? >
The following article contains some useful information about this: Chromium API keys on Debian -- http://lwn.net/Articles/570485/
signature.asc
Description: OpenPGP digital signature
