Delivery-Date: Thu, 19 Feb 2015 03:01:44 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 420CC1E02B3
	for <archiver@seul.org>; Thu, 19 Feb 2015 03:01:43 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5801D33306;
	Thu, 19 Feb 2015 08:01:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9F3A733138
 for <tor-talk@lists.torproject.org>; Thu, 19 Feb 2015 08:01:34 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id eR1f3HZbn4Yg for <tor-talk@lists.torproject.org>;
 Thu, 19 Feb 2015 08:01:34 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 77EE033121
 for <tor-talk@lists.torproject.org>; Thu, 19 Feb 2015 08:01:31 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 70F3640EDF
 for <tor-talk@lists.torproject.org>; Thu, 19 Feb 2015 08:01:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1424332888; bh=sMiB98oNlQF8H7wsNWmotAgFR/6/WXOJkza0B6SPISg=;
 h=Date:From:To:Subject:From;
 b=UmCALRKsUWKHWjt9j1HTwwKVe5ydoLQfQmTOS+k+XP53pNcmg42GvObvOs9k3GVdA
 EasHmqZVFT8WEv1sp+L8BHNnSd0s5Iy6pfawVqIDSSgbsdqyAYtz8dsUJRp4bpWkV0
 bJam5xfTd7uAeJO1ClRFBmJFIlQCnLWuSLqFCRAg=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: luisg) with ESMTPSA id 2C1E922747
Message-ID: <54E59856.7080006@riseup.net>
Date: Thu, 19 Feb 2015 03:01:26 -0500
From: Luis <luisg@riseup.net>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
Subject: [tor-talk] Tor Browser Bundle with Chromium
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

What are the reasons that makes building a Tor Browser using Chromium
not such a good idea? I recall reading somewhere that while making a Tor
Browser with a Chromium base would have its benefits due to Chromium's
superior security model (i.e. sandboxing), there are "serious privacy
issues" that would have to be solved to make that possible.
My question is what are those issues? What is preventing someone from
digging out all the Google integration and possible privacy-endangering
features and making a Tor Browser Bundle out of it?

--Luis
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

