Delivery-Date: Fri, 11 Mar 2016 07:19:11 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,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 690281E0113;
	Fri, 11 Mar 2016 07:19:09 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D52B339D58;
	Fri, 11 Mar 2016 12:19:03 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5EED639CBE
 for <tor-talk@lists.torproject.org>; Fri, 11 Mar 2016 12:19: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 cqKkbSYA75hy for <tor-talk@lists.torproject.org>;
 Fri, 11 Mar 2016 12:19:00 +0000 (UTC)
Received: from smtp14.openmailbox.org (smtp14.openmailbox.org [62.4.1.48])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 3052C39CA7
 for <tor-talk@lists.torproject.org>; Fri, 11 Mar 2016 12:19:00 +0000 (UTC)
Received: by mail2.openmailbox.org (Postfix, from userid 1004)
 id 9F7182ACD95A; Fri, 11 Mar 2016 13:18:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org;
 s=openmailbox; t=1457698736;
 bh=iYkiOBIIYOLuMCKoP2U7JQN7IFitZ67xZlJ4NzQ8ViY=;
 h=Date:From:To:Subject:In-Reply-To:References:From;
 b=TeLFz6CV30OTm4a4z7SC51k5bcDJwAZrihXMKGwviScYN4jVA5Atvwhh4m+YUNso+
 3SrfffY0Sraz/OFMh8gt9RhGVNd+mtaBky/ARcmwFI0RWmyvinhPcmJwGPw2PjyUfM
 HFqT+G5p19KA/bAmH5EAtJsiQYcVAxitTyps7HuA=
Received: from www.openmailbox.org (openmailbox-b2 [10.91.69.220])
 by mail2.openmailbox.org (Postfix) with ESMTP id 6B1542ACD95A
 for <tor-talk@lists.torproject.org>; Fri, 11 Mar 2016 13:18:46 +0100 (CET)
MIME-Version: 1.0
Date: Fri, 11 Mar 2016 12:18:46 +0000
From: blobby@openmailbox.org
To: tor-talk@lists.torproject.org
In-Reply-To: <20160311001141.GL8732@moria.seul.org>
References: <786268.93027.bm@smtp140.mail.ir2.yahoo.com>
 <CAAd2PDJ4p1GZUsYJF4Rsu6FR+SfetxnngRjxFvSdpkh7MKVDeg@mail.gmail.com>
 <20160311001141.GL8732@moria.seul.org>
Message-ID: <ab5c2fd25b97504c2a0fd1cee72fa02e@openmailbox.org>
X-Sender: blobby@openmailbox.org
User-Agent: Roundcube Webmail/1.0.6
Subject: Re: [tor-talk]
 =?utf-8?q?Why_does_parameter_=22StrictExitNodes=22_exi?=
 =?utf-8?b?c3Q/?=
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 2016-03-11 00:11, Roger Dingledine wrote:
> 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

AIUI:

StrictNodes 1
ExitNodes {us}
ExitNodes BigSexyBanana

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

