Delivery-Date: Sun, 25 Jan 2015 02:18:05 -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.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,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 0C9E51E04AF
	for <archiver@seul.org>; Sun, 25 Jan 2015 02:18:02 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 295B332C0F;
	Sun, 25 Jan 2015 07:17:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B4E3432C0F
 for <tor-talk@lists.torproject.org>; Sun, 25 Jan 2015 07:17:46 +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 F30tVTSFi1jh for <tor-talk@lists.torproject.org>;
 Sun, 25 Jan 2015 07:17:46 +0000 (UTC)
Received: from mx03.mykolab.com (mx01.mykolab.com [95.128.36.1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 81DD332B99
 for <tor-talk@lists.torproject.org>; Sun, 25 Jan 2015 07:17:46 +0000 (UTC)
X-Virus-Scanned: amavisd-new at kolabsys.net
Message-ID: <54C49889.3030004@mykolab.com>
Date: Sun, 25 Jan 2015 02:17:29 -0500
From: Libertas <libertas@mykolab.com>
To: tor-talk@lists.torproject.org
References: <54C3C353.7020709@whonix.org> <54C40BC0.7020601@mykolab.com>
 <54C47651.6040100@whonix.org>
In-Reply-To: <54C47651.6040100@whonix.org>
Subject: Re: [tor-talk] How to make TBB useable as "system Tor", as Tor,
 Vidalia, pluggable transports system level replacement?
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>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============8622948447223313482=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============8622948447223313482==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="ge04SVjISnC8CPJDimTcdqFnqJRtH55dK"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ge04SVjISnC8CPJDimTcdqFnqJRtH55dK
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 01/24/2015 11:51 PM, Patrick Schleizer wrote:
> This feature wouldn't make anything worse for regular TBB users. Just
> those who would like to use it as "system Tor" would be free to do so.

Remember that every TB user that is identifiable because they don't go
with the flow is one less fish in the school.

>> Having other traffic (chat, email
>> client, etc.) routed through the same Tor instance would greatly
>> decrease the traffic anonymity.
>=20
> That's what additional SocksPort's and stream isolation are for.

At that point, why not just use a separate daemon?

I hope someone who was involved in making these decisions comments on
this. I don't see any need to make these changes, as they will only harm
the browser's anonymity.

Also, have you checked out the network settings in the Advanced tab of
TB's preferences? By default, it's configured to use its SOCKS proxy at
127.0.0.1:9150. If you need a different configuration for Whonix, maybe
you could just patch the browser config as needed? Being more explicit
about your ultimate goal would help.


--ge04SVjISnC8CPJDimTcdqFnqJRtH55dK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUxJiJAAoJELxHvGCsI27NXKsQAI0N3At0fP3lZ4X8MgbXDzGH
WDF/DBNxmTggmmVwEijA8tKWjbaPt+ZarcE1riblU3wWjqA4HZ2Y6ZEdibGfT+wa
YakS/kIafR7vSu0JZY7yN+OFe+zJDzmHR99Wo+cyjEad5NFzp6qhao7AI77c+PWa
YeJHmUHWHEzGjdkV7Rm4eNgR2GJY6Ngkd5ze4Pw+0xCI7VtQUPmcURhZ7noCi7qb
576A9vozDzROY7/+dwSp+oV2MLWxHnamg4fwxln+gEjMbnPfTgtC4A1Haz1CwQJc
EQ+0/zx+C6CpSniQ+lNFfAhNbH5SU1Kz+sFOmE21/lZ443uHVa7lQ3b25ppFYFZA
IjqTnF//xgX0MwUNBwP8ZHWZFTs1QGZLNTXfA873jYlJgHWb4xKjWS7d1EdbMwm7
ILvT5KWqJUtQbkDxmF46X5U9V6nGSYSJOvkuBSvzwb97hVWyQUBJK6vCfLgG9EZv
JKJGVGbiA4AGjlAQGzWPxURFL1H3g5kVZPgmDjKjNpNGpS7DBxJiwoGXrHAAvLj0
EbTcMFt0/Blsm/BmmRrbmbJuOXRfjtZO5lCpQJe8ybMafMTDZsziqn27N5wy8VyH
4FDxKwodl0lIPEWjhOKkT/IrgRanBwZJQkOG6nTjoHTWaFFwFCExMTrVkRqeUB2q
cII1j+iJtXlUlLqRwkXm
=MmGp
-----END PGP SIGNATURE-----

--ge04SVjISnC8CPJDimTcdqFnqJRtH55dK--

--===============8622948447223313482==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
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

--===============8622948447223313482==--

