Delivery-Date: Mon, 20 Jul 2015 20:49:08 -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 ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 916A71E07F2;
	Mon, 20 Jul 2015 20:49:06 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E267A21FE7;
	Tue, 21 Jul 2015 00:48:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 767F32142C
 for <tor-talk@lists.torproject.org>; Tue, 21 Jul 2015 00:48:56 +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 SkVZW27T35ev for <tor-talk@lists.torproject.org>;
 Tue, 21 Jul 2015 00:48:56 +0000 (UTC)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com
 [IPv6:2607:f8b0:400d:c09::230])
 (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 5074020B5F
 for <tor-talk@lists.torproject.org>; Tue, 21 Jul 2015 00:48:56 +0000 (UTC)
Received: by qkfc129 with SMTP id c129so80808992qkf.1
 for <tor-talk@lists.torproject.org>; Mon, 20 Jul 2015 17:48:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=from:to:references:in-reply-to:subject:date:message-id:mime-version
 :content-type:content-transfer-encoding:thread-index
 :content-language;
 bh=yircy8upYSFV8UqgZ9PBy8oG1nIOs46yGPmDC5pInyc=;
 b=KxWyD7sI1SkKJBWXjrPduP+xtys+Fdupwv05V5nq5f3k93o1pYQkyOiRwnRrIb/f1C
 C5GEYO2upYiZWW01AtbCvX1z0cXNwHq27WqarnvBtn9r87nXrfIuPCMdGhhbXiSzWOhp
 mF312xX6D//CM4lo865hfmPmzZMii4aUKgsXxwS7eI2zFyVMl1cFt0ZZJW5p9c02oBpa
 5I9DjkYfYy3Wftjpt9UF+OjiYzyrNdqsSAnw8DPUC8Fy1Z0jycUSpLansjomonFVcFcK
 5rJxW2cbtdAOQB9DCQP0RlpL/8Yp6lYeaN38Ti6oA80RhNBN1gc2EmYWButc5h0acP/d
 xLBA==
X-Received: by 10.140.39.17 with SMTP id u17mr50854855qgu.5.1437439733990;
 Mon, 20 Jul 2015 17:48:53 -0700 (PDT)
Received: from APT510 (c-73-163-4-150.hsd1.md.comcast.net. [73.163.4.150])
 by smtp.gmail.com with ESMTPSA id e60sm7442051qge.14.2015.07.20.17.48.53
 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
 Mon, 20 Jul 2015 17:48:53 -0700 (PDT)
From: "Allen" <allenpmd@gmail.com>
To: <tor-talk@lists.torproject.org>, "'me'" <tortalk@couldbe.securecoffee.com>
References: <MTAwMDAzNS5jb3VsZGJl.1437415566@quikprotect>
 <07b401d0c31b$5347c490$f9d74db0$@gmail.com>
 <MTAwMDAzMy5jb3VsZGJl.1437438707@quikprotect>
In-Reply-To: <MTAwMDAzMy5jb3VsZGJl.1437438707@quikprotect>
Date: Mon, 20 Jul 2015 20:48:51 -0400
Message-ID: <082e01d0c34f$03b4aef0$0b1e0cd0$@gmail.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIbAhzOiC0lv4YdgILKzTyWKKMVfAGm0jv2AeaM2Z2dNCvYcA==
Content-Language: en-us
Subject: Re: [tor-talk] Hidden Service and exit circuit questions?
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>

> Since there is already an established circuit between the machine running
the Tor service and an exit node, I'm thinking that the exit node may be
able to use the existing circuit to access the HS port over the 3-hop
circuit without ever going through the normal 6-hop rendezvous?

You could check the source code, but I would guess that if a circuit is not
built using the rendezvous protocol, then packets coming in on that circuit
are not forwarded back to the hidden service port on the localhost.  More
generally, packets coming in on any circuit are forward only to the local
port for which the circuit was setup to proxy, i.e., there is no "crosstalk"
between circuits.


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

