Delivery-Date: Mon, 15 Jun 2015 15:27:01 -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 223C11E0A34;
	Mon, 15 Jun 2015 15:26:59 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 142F636488;
	Mon, 15 Jun 2015 19:26:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 785B836474
 for <tor-talk@lists.torproject.org>; Mon, 15 Jun 2015 19:26:48 +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 b_wdatkCg7VD for <tor-talk@lists.torproject.org>;
 Mon, 15 Jun 2015 19:26:48 +0000 (UTC)
Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com
 [IPv6:2607:f8b0:4002:c07::22a])
 (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 523343645D
 for <tor-talk@lists.torproject.org>; Mon, 15 Jun 2015 19:26:48 +0000 (UTC)
Received: by ykfl8 with SMTP id l8so64930399ykf.1
 for <tor-talk@lists.torproject.org>; Mon, 15 Jun 2015 12:26:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=3WIj3ICll5magcXCQUSc4E2X3mvlWdQ1pur8XCnBEM0=;
 b=n2oH61PaMCt0XpcGh5/GF6hLgG/w0+kWUV/KOExM5g1fAcdXJFuze4rcqfxjnUxsXb
 V/+5RBYPKTJd1b33vav1JB1nMxbpNPueS+wUgmruZyj873e82XpOlvRsNue1Aqzs5DnR
 GzYkYzIQbbvtGaOQ2UqluwYUPwLXaWTv3cEV5MYGj7z/wmQ1IEneHVrVqyqbiQAGjD46
 61Ml/pf/NAstoQGpgj3l8dCIrJK34kM8iYzqmeOCyCUomuaWdlk6C0rnwAu/HDiIPjR1
 9NLmA7E2RQ7NCS3FqVGVlYC85SQIR0fqs3LAN+MD7mX8/0n87wVFVyRfSR0RYw6Jj0Vy
 VjWQ==
MIME-Version: 1.0
X-Received: by 10.129.84.86 with SMTP id i83mr36205298ywb.77.1434396405984;
 Mon, 15 Jun 2015 12:26:45 -0700 (PDT)
Received: by 10.13.212.202 with HTTP; Mon, 15 Jun 2015 12:26:45 -0700 (PDT)
Date: Mon, 15 Jun 2015 19:26:45 +0000
Message-ID: <CADtD-Z9=q3PK1LrYPth1iDSk3Oc_4VkNyU1eY2G523G2bEMo9g@mail.gmail.com>
From: Jeffrey Burdges <burdges@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] Anyone actually using a local exitpolicy?
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>

There is a comment in the torrc man page that exit policies can target the
local machine or private networks, like say :

ExitPolicy accept 127.0.0.1:80
ExitPolicy reject private:*

Does anyone actually do this? If so, how does one use it?

There are no ip address limits specified in the consensus according to :

egrep "^p6? " /var/lib/tor/cached-microdescs | grep ':'

There are several possibilities for what this means :

(1) Tor does not bother to list such exits because their private.  duh!

(2) Private exit operators suppress inclusion using another option, or

(3) nobody does this.

Assuming the awnser is (1) then how does one use the access the local exit
created?  Is it perhaps : set Nickname not the server, set AllowDotExit 1
on the client. And access localhost.foobar.exit:80 or similar?
Thanks,
Jeff
-- 
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

