Delivery-Date: Thu, 10 Mar 2016 17:39:32 -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.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 6E9F31E0520;
	Thu, 10 Mar 2016 17:39:30 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6B8A939DE5;
	Thu, 10 Mar 2016 22:39:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1962B39DDD
 for <tor-talk@lists.torproject.org>; Thu, 10 Mar 2016 22:39:23 +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 KhzSwbgK5s4p for <tor-talk@lists.torproject.org>;
 Thu, 10 Mar 2016 22:39:23 +0000 (UTC)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com
 [IPv6:2607:f8b0:4003:c01::235])
 (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 EB67539DD5
 for <tor-talk@lists.torproject.org>; Thu, 10 Mar 2016 22:39:22 +0000 (UTC)
Received: by mail-ob0-x235.google.com with SMTP id ts10so95975711obc.1
 for <tor-talk@lists.torproject.org>; Thu, 10 Mar 2016 14:39:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
 bh=OHXrIEeprQt2y8W5Ac2J5rx98VoMe6YqVi/qBDgKleg=;
 b=ccLkoTL55wZRddSYStPswecxlI8EwtuEAc9z5ukownKaUavbAtG8sQVZj8QwDH1W8n
 GhyuYbL5kkWCZt8wlbOSLxcraiJEaRaGE8vP4FUPbycuRudGkNNljR3OksSF272ZrlE+
 dc0G5na9nVopdfTK+9oZmM+SGRzjySOnvmvbcIzo1V/2UjdPW3wi8cqEMqPqLN+ho3oI
 BUp5V5AD1yIJQo6afznW3EBZmevofW7paGQde9Dg1EAaBkokBzXvUD3Tvd9jFjnf2qA0
 8BaPY7mQDDzNSYWRvMVk/r0alyTF5RUCGMwz6jGIh/NRbWFH0AnGCSYmrRKOHuguwlMa
 hI1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to;
 bh=OHXrIEeprQt2y8W5Ac2J5rx98VoMe6YqVi/qBDgKleg=;
 b=ARVsA6mc1gWlcTT/Mkh3dREv8Kjwheje6usguMMBqHkbPzuc1/62Ji5SSUlEXmz+Ak
 AYd629Xc23AjfFEPZO2TrGoO+ykCkEeCyd9Z5e+CAyzcZneQrtztDd5XI1v3ZLoY/9HP
 U3os+kEmwBW5WRN+q4V4XfanJ/Swmi1qIFBLx6BcjjkDeK1at7xRclNCuF8InhPq5Zm6
 dRko5kPT09jGhFwcpBSs3eVuKh+s2cGcYj8wINhIpLWshaJi8HyfR+r0jB7WYd7vqIBC
 4gP9JcopSE/fJksHmfc9R1lHUrSdMHqEMWBGEtDzOfEsHKLBPrKobsDig3uVsdm/N5rI
 uGEA==
X-Gm-Message-State: AD7BkJKOBdxFfnGmJJm2DgK3ZiJ/mzC8lmqH5pBcKkWiXMvekqsLJyVbgGaHZngwcqbKmk4csgcCOL+Oyp0TSA==
MIME-Version: 1.0
X-Received: by 10.60.35.163 with SMTP id i3mr3873784oej.36.1457649560561; Thu,
 10 Mar 2016 14:39:20 -0800 (PST)
Received: by 10.76.70.229 with HTTP; Thu, 10 Mar 2016 14:39:20 -0800 (PST)
In-Reply-To: <786268.93027.bm@smtp140.mail.ir2.yahoo.com>
References: <786268.93027.bm@smtp140.mail.ir2.yahoo.com>
Date: Thu, 10 Mar 2016 14:39:20 -0800
Message-ID: <CAAd2PDJ4p1GZUsYJF4Rsu6FR+SfetxnngRjxFvSdpkh7MKVDeg@mail.gmail.com>
From: Green Dream <greendream848@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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>

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. ;-)
-- 
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

