GNU bug report logs -
#28004
Chromium
Previous Next
Reported by: Marius Bakke <mbakke <at> fastmail.com>
Date: Mon, 7 Aug 2017 20:00:01 UTC
Severity: normal
Done: Marius Bakke <mbakke <at> fastmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Tobias Geerinckx-Rice <me <at> tobias.gr> writes:
> Marius!
>
> On 2018-04-24 20:08, Marius Bakke wrote:
>> The other remaining issue is that some data is sent to Google whenever
>> you start the browser for the first time.
>
> Sounds great! What data, exactly?
I haven't MITM'd it to check, unfortunately. Help wanted!
The reason I don't think it's a blocking issue, is because Chromium is
a massive project and I cannot guarantee that it will never "call
home". So while I am intent on fixing the issue, especially since it's
easy to test (chromium --user-data-dir=/tmp/foo), it's just one of many
"call home" scenarios/antifeatures. And if you enable extensions or log
in all bets are off. Even Inox, which goes great lengths to de-google
it, admits that they can't guarantee privacy.
Other scenarios include checking for IPv6 availability, testing for
captive portal, etc. And I think it even falls back to Google DNS if
the system resolver is unresponsive. :-(
[signature.asc (application/pgp-signature, inline)]
This bug report was last modified 6 years and 154 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.