Delivery-Date: Sat, 21 Jun 2014 15:57:09 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 C5CDE1E0A6C
	for <archiver@seul.org>; Sat, 21 Jun 2014 15:57:07 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8CF0D30230;
	Sat, 21 Jun 2014 19:57:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 72D032FCE0
 for <tor-talk@lists.torproject.org>; Sat, 21 Jun 2014 19:44:58 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 oB42gk7O4EST for <tor-talk@lists.torproject.org>;
 Sat, 21 Jun 2014 19:44:58 +0000 (UTC)
X-Greylist: delayed 907 seconds by postgrey-1.34 at eugeni;
 Sat, 21 Jun 2014 19:44:58 UTC
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 3B51A2FCD2
 for <tor-talk@lists.torproject.org>; Sat, 21 Jun 2014 19:44:58 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <gno-or-talk-2@m.gmane.org>) id 1WyQyx-0007lG-Ac
 for tor-talk@lists.torproject.org; Sat, 21 Jun 2014 21:29:47 +0200
Received: from 67-1-204-186.tcso.qwest.net ([67.1.204.186])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Sat, 21 Jun 2014 21:29:47 +0200
Received: from scar by 67-1-204-186.tcso.qwest.net with local (Gmexim 0.1
 (Debian)) id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Sat, 21 Jun 2014 21:29:47 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: tor-talk@lists.torproject.org
From: scar <scar@drigon.com>
Date: Sat, 21 Jun 2014 12:29:32 -0700
Lines: 21
Message-ID: <lo4mev$r2a$1@ger.gmane.org>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 67-1-204-186.tcso.qwest.net
X-Archive: encrypt
Subject: [tor-talk] Tor and cloudflare servers
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>

hi i have been running an exit node for several years now.  from time to
time i will get banned/warned from sites who decide they want to
ban/block Tor from their servers.  usually this is resolved by blocking
access to said sites in my exit policy, and ensuring the sites are using
a tool like TorBulkExitList.py to determine nodes that can access their
site.

now i am in a similar situation with a site that uses cloudflare, and
thus currently has 6 different IP addresses according to simple linux
'host' tool.  i've blocked all of these addresses in my exit policy.
the admins of the site claim that these IP addresses can change "every
minute based on demand, attacks, and location" and that "Someone
accessing from another location [besides mine, maybe another country]
will get a different set of result, and it is not constant."

is there truth to these claims?  how can i properly and completely block
access to the site (or other sites using cloudflare or other similar
services) in my exit policy?  i've basically been given an ultimatum to
stop running my exit node while accessing the site or be banned from the
site.


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

