Delivery-Date: Thu, 30 Oct 2014 10:55:19 -0400
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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD 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 44DB41E0C96;
	Thu, 30 Oct 2014 10:55:16 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id AC3B23121C;
	Thu, 30 Oct 2014 14:55:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E0F613112A
 for <tor-talk@lists.torproject.org>; Thu, 30 Oct 2014 14:55:08 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 flascu-6Zfy2 for <tor-talk@lists.torproject.org>;
 Thu, 30 Oct 2014 14:55:08 +0000 (UTC)
X-Greylist: delayed 376 seconds by postgrey-1.34 at eugeni;
 Thu, 30 Oct 2014 14:55:08 UTC
Received: from smtp-gw11.han.skanova.net (smtp-gw11.han.skanova.net
 [81.236.55.20])
 by eugeni.torproject.org (Postfix) with ESMTP id 833F530F17
 for <tor-talk@lists.torproject.org>; Thu, 30 Oct 2014 14:55:08 +0000 (UTC)
Received-SPF: softfail (smtp-gw11.han.skanova.net: domain larsluthman.net does
 not designate 78.73.33.144 as permitted sender)
 identity=mailfrom; receiver=smtp-gw11.han.skanova.net; client_ip=78.73.33.144;
 envelope-from=mail@larsluthman.net; helo=[192.168.1.101]; 
Received: from [192.168.1.101] (78.73.33.144) by smtp-gw11.han.skanova.net
 (8.5.142.07) id 5435B849006B2F8D for tor-talk@lists.torproject.org;
 Thu, 30 Oct 2014 15:48:47 +0100
Message-ID: <1414680507.14332.1452.camel@miskatonic>
From: Lars Luthman <mail@larsluthman.net>
To: tor-talk@lists.torproject.org
Date: Thu, 30 Oct 2014 15:48:27 +0100
In-Reply-To: <CAJwFvsWUsTVit2E21Pn9m8vwh6qPXtG31JJso8RRP3ULw84Ozw@mail.gmail.com>
References: <CAJwFvsWUsTVit2E21Pn9m8vwh6qPXtG31JJso8RRP3ULw84Ozw@mail.gmail.com>
X-Mailer: Evolution 3.4.4-3 
Mime-Version: 1.0
Subject: Re: [tor-talk] Can Tor run over Tor?
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: multipart/mixed; boundary="===============4941025572555563015=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============4941025572555563015==
Content-Type: multipart/signed; micalg="pgp-sha512";
	protocol="application/pgp-signature"; boundary="=-MuQgCAgg3+1bVAE1RFX9"


--=-MuQgCAgg3+1bVAE1RFX9
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, 2014-10-30 at 10:02 -0400, Tyler Hardin wrote:=20
> I'm sitting here with my computer using my phone's internet via USB
> tethering and have Orbot on my phone and TBB on my computer. If I set Orb=
ot
> to tunnel all tethered traffic through Tor and then open up TBB, am I
> really running Tor over Tor?
>=20
> If so, has anyone ever thought about the pros/cons of this? Obviously, it=
's
> exponentially more inefficient. But is it any more secure?

I have done it accidentally with a misconfigured transparent proxy that
sent its own Tor traffic to its own transparent proxying port. It
worked, though a bit slower (as expected).

I don't think it would be any more secure. The most serious publically
known attacks against the anonymity of Tor users (browser bugs etc
notwithstanding) are correlation attacks where the attacker compare
traffic at the client end with traffic at exit nodes and see if it looks
similar in timing and data sizes. A six-relay circuit (which is what you
get when running Tor over Tor) doesn't change that at all.

An attack where the traffic is actually traced all the way through the
Tor relays would be harder, but those are probably not the attacks we
should be worrying about in the first place. And a longer circuit may
make it more likely that an attacker can correlate traffic _inside_ the
circuit as well.


--ll


--=-MuQgCAgg3+1bVAE1RFX9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----

iQIcBAABCgAGBQJUUk+8AAoJEFhtKt5tmcUSvXkQAJzecRf2Ft856kC3huDvH9Wc
RXGS5XFVP2gBUhyudoY3kA0RfF2HDAlsfQMNtRl5Mg6TuWB2ORanZ3iUCKwcYHoE
httsa4nK29A1ch7VtE42hTpz21duz7opkY6qyVOVLr1dBk0tUKS/exhleLDYdmOL
Lb5e1RIFFwhwwlvS41d8arHuhX3u2db0MufjCE06dHgAYhL+KH2XSNe1kRp7FS2B
2hWqUzm2Tn1tUFeECOn0KRK1LwU9d2qFpFmkIqfE+lNsZlh+OnyHzCB7Qh6NylEx
aMMnhiB7l7E+nQqP1OLX3/9S6lsQm92kP/tMPpWrRo2sOAoGqAlQoVXuCvdj003u
qhkYglmOiVSNOZZEfiyeP3RKIbysE7OQ+Tet5529thZUrP2I+Kmp6hIz5xqAk6a8
qa+dWC6UFOp3LYAZ1egQim0Lg+Pk2ZDDulF9l3t3ydnQbDGEniIx+6FDq6XPxLgx
kC8k1U53ojqumItFdSejvkMH3RmyaNfQlp/+ssZfEC5LFSeWUK8/0DVOa2308Fpl
AfxhMjVIIaP28n7eIK6mu6nnW7+QguUwNdbfDkaFso4uN43gfxm6V8veOF9L6RkP
5Q9BENv/RbmvPwWVTIidE8FGw3XX2+0Xvla3J8AVXs5TkOLqmySOKjjCbdzIwINO
fqTREkNIMSGJD5n5SB7I
=rcjN
-----END PGP SIGNATURE-----

--=-MuQgCAgg3+1bVAE1RFX9--


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

--===============4941025572555563015==--

