Delivery-Date: Mon, 07 Mar 2016 05:52:20 -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=-2.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,HK_RANDOM_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 D84C11E04EC;
	Mon,  7 Mar 2016 05:52:18 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id EDF5131E33;
	Mon,  7 Mar 2016 10:52:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 4E89F31E39
 for <tor-talk@lists.torproject.org>; Mon,  7 Mar 2016 10:52:09 +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 hcRrVJ-wZU70 for <tor-talk@lists.torproject.org>;
 Mon,  7 Mar 2016 10:52:09 +0000 (UTC)
Received: from latitanza.investici.org (latitanza.investici.org
 [IPv6:2001:888:2000:56::19])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.autistici.org",
 Issuer "Autistici/Inventati Certification Authority" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 2406D31E33
 for <tor-talk@lists.torproject.org>; Mon,  7 Mar 2016 10:52:06 +0000 (UTC)
Received: from [82.94.249.234] (latitanza [82.94.249.234]) (Authenticated
 sender: fkqqrr@autistici.org) by localhost (Postfix) with ESMTPSA id
 6D3E81200E7
 for <tor-talk@lists.torproject.org>; Mon,  7 Mar 2016 10:52:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=autistici.org;
 s=stigmate; t=1457347922;
 bh=wh/iyeW7EkRotF2BzkxtY2cz2M2OVN9Xs40TwJPZMeg=;
 h=From:To:Subject:Date;
 b=GwBoFrPxa7UmvtBx48AiQWL8x1lm/4HQfzACyfwGYhV3Orb3h1V6+NED1mEEWrNEp
 xehK6+cuK1lj01zYc5XJ/V8k7VjoJrYri4biHTvx/DgnKNVch2SP4by4+hYYN6eKE7
 P+Aj6nZ2Rkackm34Qae4g1x8gX/sXHhoYIldifQ4=
From: fkqqrr@autistici.org
To: tor-talk@lists.torproject.org
Date: Mon, 07 Mar 2016 18:37:19 +0800
Organization: GNU/Linux
User-Agent: Emacs/Gnus
Message-ID: <8760wy4l4y.fsf@zhtux.jiantu.boxes>
MIME-Version: 1.0
Subject: [tor-talk] cloudflare blocks connection
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>


I am using Tor + firefox to acess destination site.

For Tor part, I added a `Socks5Proxy'. If I am right, the actual
connection circuit is: `firefox - tor - socks5 proxy - entry node
- intermediate nodes - exit node - target site'.

What's more, my computer use TorDNS to resolve all hostnames
resolving.

When visit some target sites, cloudflare asked to fill in CAPTCHA
verification in the very first days. After that, cloudflare
totally blocks my connection even I correctly pass the CAPTCHA. It
just reminds:

  Sorry, you have been blocked
  You are unable to access target-site

In the bottom, `Cloudflare Ray ID and Tor IP is displayed. I just
surf the target site and do nothing else.

AFAIK, Tor choose a new circuit every around 10 minutes. That
means my computer choose different exit nodes on each
connection. I think neither cloudflare nor target site can
identify my computer (i.e. fingerprint).

To cloudflare and/or target site, my computer is the same as other
Tor computers. The only common is we might share the same set of
exit nodes occasionally.

How cloudflare block my connection?

Does it identity my computer fingerprint to block?

Does it just block Tor's exit nodes? (that would mean others using
Tor cannot connect to target site either)

-- 
Hello, world
-- 
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

