Delivery-Date: Thu, 10 Mar 2016 19:11:53 -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.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 422BF1E0E36;
	Thu, 10 Mar 2016 19:11:52 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E645D39E72;
	Fri, 11 Mar 2016 00:11:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9ACE139DB0
 for <tor-talk@lists.torproject.org>; Fri, 11 Mar 2016 00:11:44 +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 NMvB2HxDnwqd for <tor-talk@lists.torproject.org>;
 Fri, 11 Mar 2016 00:11:44 +0000 (UTC)
Received: from khazad-dum.seul.org (khazad-dum.csail.mit.edu [128.31.0.47])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "moria.seul.org", Issuer "moria.seul.org" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 837B039621
 for <tor-talk@lists.torproject.org>; Fri, 11 Mar 2016 00:11:44 +0000 (UTC)
Received: by khazad-dum.seul.org (Postfix, from userid 501)
 id 922C71E0E36; Thu, 10 Mar 2016 19:11:41 -0500 (EST)
Date: Thu, 10 Mar 2016 19:11:41 -0500
From: Roger Dingledine <arma@mit.edu>
To: tor-talk@lists.torproject.org
Message-ID: <20160311001141.GL8732@moria.seul.org>
References: <786268.93027.bm@smtp140.mail.ir2.yahoo.com>
 <CAAd2PDJ4p1GZUsYJF4Rsu6FR+SfetxnngRjxFvSdpkh7MKVDeg@mail.gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CAAd2PDJ4p1GZUsYJF4Rsu6FR+SfetxnngRjxFvSdpkh7MKVDeg@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-12-10)
Subject: Re: [tor-talk] Why does parameter "StrictExitNodes" exist?
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 Thu, Mar 10, 2016 at 02:39:20PM -0800, Green Dream wrote:
> By default (i.e., StrictNodes is false) Tor will bypass your declared
> ExitNodes if it needs to do so in order for traffic to reach its
> destination. Imagine the scenario where all the exit nodes in your
> ExitNodes criteria have strict exit policy and they have no way to route
> your traffic to its destination. With StrictNodes set to True, Tor won't
> ever look for another exit, and this traffic won't be routable.
> 
> Going from memory, don't quote me. ;-)

No, this is wrong. StrictNodes has no effect on ExitNodes.

This is maybe a better description than the previous one I tried:
https://gitweb.torproject.org/tor.git/tree/ReleaseNotes?id=tor-0.2.2.32#n124

--Roger

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

