Delivery-Date: Sun, 15 May 2016 07:36:12 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_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 AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 5BAA01E0313;
	Sun, 15 May 2016 07:36:10 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BAE46398CC;
	Sun, 15 May 2016 11:36:04 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F1E2E3703F
 for <tor-talk@lists.torproject.org>; Sun, 15 May 2016 11:36:00 +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 cdOjSPTDrB7V for <tor-talk@lists.torproject.org>;
 Sun, 15 May 2016 11:36:00 +0000 (UTC)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com
 [IPv6:2607:f8b0:4002:c05::22b])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id C83C6283A6
 for <tor-talk@lists.torproject.org>; Sun, 15 May 2016 11:36:00 +0000 (UTC)
Received: by mail-yw0-x22b.google.com with SMTP id g133so139273155ywb.2
 for <tor-talk@lists.torproject.org>; Sun, 15 May 2016 04:36:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=from:content-transfer-encoding:mime-version:subject:message-id:date
 :references:in-reply-to:to;
 bh=K2Km1mSoba4gxz0Gc78BkIvYJrW382O9Wsy+78TtqfQ=;
 b=XJWP6f+OXjAIFTixnANTkIAyfKRL7eu12KjTLotqdc4Sty32SOujOzQRIBSr9uuJeZ
 InJCovIJQD3kQ4FrvjMqKT1kfMx7CrjnwqpL//zvKJqBubrPJ0M9VwXFogpek6JijrMw
 Zo9ZMwIqGPMLZD+2izCpgh/VEZx4QNnNvFG4GiZ/WwZNOBpOrgNOpOsFQhZSId697Imu
 P5ARm0q/8cHb04FSv7ItX05dtYAmBc2+503f01Xo+6y3gCHfgr4ET+jg7tUZYDjVGP5s
 ST8Uv359qkIZfymjVATH3WmtdGPuCMeCO/BaLjz7SK2x9stf3mX7OF6+DO77viWsn6re
 LPXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:content-transfer-encoding:mime-version
 :subject:message-id:date:references:in-reply-to:to;
 bh=K2Km1mSoba4gxz0Gc78BkIvYJrW382O9Wsy+78TtqfQ=;
 b=FVCg3Jdf7l8eA3VaqmuV497eeundlYDitj2YnpcnkVi8gcv7Sti5NjPiOmydrQqi7y
 3+KeOfEvuZSk0jUTKtI78nXbAubeDu92neZs+NFlVd0NTbbCRqvmiIda9Gv+kNSeqkz9
 TlzopmFfwW1dhv4tdPmuojceeons286HrDID2Hh7fgzV9r1XoqxfN2x4415ofdnfjNdM
 4OdPaa0WmgOTJ2dTyN6X0MYm6nRfwnTkApu+H8jNsmbI2rexfkH5c0J7x/oXiaAbfjDP
 ytKvPeB5Hj2H7YOGhrAMQxsNh54CTcFWYk8S1QfbdnQwuP7zFTJcpQDdsfQcRct4OkL+
 4DFw==
X-Gm-Message-State: AOPr4FVp2HmPMezAjd7ISRbvSzwGNR2GtTNgopyK34dWUBtXhV52QUTHenXxI6dORIDfaA==
X-Received: by 10.129.145.214 with SMTP id i205mr13203444ywg.192.1463312158081; 
 Sun, 15 May 2016 04:35:58 -0700 (PDT)
Received: from [172.48.102.73] ([172.56.21.36])
 by smtp.gmail.com with ESMTPSA id f129sm16112214ywd.10.2016.05.15.04.35.57
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Sun, 15 May 2016 04:35:57 -0700 (PDT)
From: moosehadley@gmail.com
Mime-Version: 1.0 (1.0)
Message-Id: <F2217794-3AD8-4A09-9E51-7BFF1ECC72DF@gmail.com>
Date: Sun, 15 May 2016 07:35:48 -0400
References: <5f278d34623e15017caa063ee0d261ae.webmail@localhost>
In-Reply-To: <5f278d34623e15017caa063ee0d261ae.webmail@localhost>
To: tor-talk@lists.torproject.org
X-Mailer: iPhone Mail (13F68)
Subject: Re: [tor-talk] Tor entry and exit nodes
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>


> On May 15, 2016, at 6:39 AM, katerimmel@sigaint.org wrote:
> 
> If an adversary (government) have in their hands some exit nodes(ex:logs
> from a VPN) can identify the entry node and then the ip of the pc
> connected?

Tor uses three nodes between the user and the destination. Each node only knows the IP of the point before it and the point after it.

For example, the entry node only knows the IP of the user and the middle node. The middle node only knows the IP of the entry node and the exit node. The exit node only knows the IP of the middle node and the destination.

An adversary would need control of all three nodes to be 100% certain of who the user is and what the final destination is.

If an adversary only controlled the exit or the entry node, they could make an educated guess by watching the amount of traffic leaving the user and arriving at the destination; but it would be impossible (or extremely difficult) to do this without extensive preparations beforehand.
-- 
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

