Delivery-Date: Mon, 20 Jul 2015 14:06:20 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 C7E731E01A3;
	Mon, 20 Jul 2015 14:06:18 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 79414354FD;
	Mon, 20 Jul 2015 18:06:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id CB68E35229
 for <tor-talk@lists.torproject.org>; Mon, 20 Jul 2015 18:06:09 +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 Te6hBdNHckZV for <tor-talk@lists.torproject.org>;
 Mon, 20 Jul 2015 18:06:09 +0000 (UTC)
Received: from mailhost.cotse.com (mail.cotse.net [66.203.85.58])
 (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 AA01234F50
 for <tor-talk@lists.torproject.org>; Mon, 20 Jul 2015 18:06:09 +0000 (UTC)
Received: from out.packetderm.com (out.packetderm.com [66.203.85.62])
 by mailhost.cotse.com (8.14.8/8.14.5) with ESMTP id t6KI66Cg082726
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
 for <tor-talk@lists.torproject.org>; Mon, 20 Jul 2015 14:06:06 -0400 (EDT)
 (envelope-from tortalk@couldbe.securecoffee.com)
Received: from localhost (localhost[127.0.0.1]) (authenticated bits=0)
 by smtp (5.7.4/5.7.4) with ESMTP id t6KI6610046368
 for <tor-talk@lists.torproject.org>; Mon, 20 Jul 2015 14:06:06 -0400 (EDT)
 (envelope-from tortalk@couldbe.securecoffee.com)
Received: from HTTP by 127.0.0.1 with HTTP; Mon, 20 Jul 2015 14:06:06 -0400
Message-ID: <MTAwMDAzNS5jb3VsZGJl.1437415566@quikprotect>
Date: Mon, 20 Jul 2015 14:06:06 -0400
From: "me" <tortalk@couldbe.securecoffee.com>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
Importance: Normal
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>

My primary question is about the established "exit circuits".

If the exit circuits are established, as they are by default, can an exit
node initiate contact with my HS without ever going through a rendezvous or
even knowing the onion address by simply using the pre-established circuit?

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

