From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55420) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1er5XO-0007Ia-KI for guix-patches@gnu.org; Wed, 28 Feb 2018 12:29:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1er5XK-0003H6-Jk for guix-patches@gnu.org; Wed, 28 Feb 2018 12:29:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:58088) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1er5XK-0003H0-GL for guix-patches@gnu.org; Wed, 28 Feb 2018 12:29:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1er5XK-0003k2-5n for guix-patches@gnu.org; Wed, 28 Feb 2018 12:29:02 -0500 Subject: [bug#28004] Chromium Resent-Message-ID: From: Marius Bakke In-Reply-To: <87k1uznqcu.fsf@gnu.org> References: <87y3qvb15k.fsf@fastmail.com> <20171010131949.y43plpzxbppvrigr@abyayala> <87lgkha2cx.fsf@gnu.org> <20171012195628.GA31843@jasmine.lan> <87shensfq6.fsf@gnu.org> <87o9p45bb6.fsf@fastmail.com> <20180104191648.custe7w3l57fvbac@abyayala> <87wp0s2ewl.fsf@fastmail.com> <20180108232042.nqjurjr2bcfl2yyc@abyayala> <87373cey5b.fsf@fastmail.com> <87vag16g5z.fsf@gnu.org> <87fu75aar5.fsf@fastmail.com> <874lnkr0vf.fsf@gnu.org> <87vaejvclc.fsf@fastmail.com> <87k1uznqcu.fsf@gnu.org> Date: Wed, 28 Feb 2018 18:28:46 +0100 Message-ID: <87zi3tt44x.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Mike Gerwitz Cc: 28004@debbugs.gnu.org --=-=-= Content-Type: text/plain Mike Gerwitz writes: > On Mon, Feb 26, 2018 at 19:18:39 +0100, Marius Bakke wrote: >> Now, when launching the browser for the first time, it *still* connects >> to Google services. After a while it also does a lookup for AdWords... > > Do you know what code initiates this? Would it be easy to remove, and > would that harm other functionality? Unfortunately, I don't know what triggers it. Feel free to try picking some of the other Inox patches and see if it makes a difference: https://github.com/gcarq/inox-patchset Inox goes great lengths to "ungooglify" the browser. I've decided against picking *all* their patches, for two reasons: 1) I'd like users to be able to use Chromium with their Google account if they wish to (although I haven't actually tested this), and more importantly: 2) More patches means more porting work every new release. Usually major versions bumps come with a plethora of security fixes, so I wish to minimize maintenance overhead. Just figuring out the changed dependencies, build flags, and GCC bugs with every release is a lot of work already. > Saying that it only runs the first time implies to me that there's a > flag, and that perhaps the flag can either be permanently set or the > conditional triggering this behavior removed. Indeed. Any help figuring out the offender is very welcome! No external connectivity in the default configuration is a goal we should strive for. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlqW5s4ACgkQoqBt8qM6 VPottwf5AXGEfvNf79MnW8g1W7l9o436utStYCIs+CJD8ZyDG5PIZQSA+BwxZ0nA 9cfS/JUwdbDjt/pk6ByU9qauCvEwC/zurhWGaUr/yJyMBHikjyn0/Cmu4hfuRGHG hUPg1XnucEgDSsaCWRH2YStgDLfR2HHaVNKNHqgIVqcgvDJiY09lH5kNQIVDPeyH TwHowGxIYm18a0gvBnxKqWQm2izQV4xGMpqv/Ub38AieSIsbv3yyHbWf0kCBfKTK bohEWn2pApWJ0a+VUinXKyh5PILaHNq0DQMGGpcZH5givh94+Y2imNeEIKtDOjqp 7DD2qTLohAxjSmMoqsg23ojCfnkbug== =gTUK -----END PGP SIGNATURE----- --=-=-=--