Delivery-Date: Thu, 31 Mar 2016 18:46:56 -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_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	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 4A31E1E0CAB;
	Thu, 31 Mar 2016 18:46:54 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 40A6E39FEE;
	Thu, 31 Mar 2016 22:46:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 8CC0239CD4
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 22:46:45 +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 Auz36U_rdecG for <tor-talk@lists.torproject.org>;
 Thu, 31 Mar 2016 22:46:45 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 6A58B39870
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 22:46:45 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 9F0541ABBED
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 22:46:42 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1459464402; bh=1xTX4weVOq45Gois2SOcaE8MZJkbthJ9/hUs/QdbBCM=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=azpF+RU+ouOF5KNUbvlVi//WGJkXc48xKM5QOTfao7X2n1ql++Yb270GA9ideLOX+
 n4BgSuhNk/OtYs2VyR4mhLw6aS2MZRdADdzolkbt53ipaphixMqf74ZOFP3eORMHRD
 snHVGn4APlmdhaeJVJ2Y3wBWELeeTdOKJYseHN+g=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 05D731C0036
To: tor-talk@lists.torproject.org
References: <20160330132105.GA8024@lapsedordinary.net>
From: Mirimir <mirimir@riseup.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56FDA8CF.1090309@riseup.net>
Date: Thu, 31 Mar 2016 16:46:39 -0600
MIME-Version: 1.0
In-Reply-To: <20160330132105.GA8024@lapsedordinary.net>
X-Virus-Scanned: clamav-milter 0.99 at mx1.riseup.net
X-Virus-Status: Clean
Subject: Re: [tor-talk] CloudFlare blog post
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>

On 03/30/2016 07:21 AM, Martijn Grooten wrote:
> CloudFlare CEO Matthew Prince just posted this blog post
> 
>   https://blog.cloudflare.com/the-trouble-with-tor/  
> 
> which I think is worth a read for people on this list.

<SNIP>

In discussion on Hacker News about why CAPTCHAs are so slow using Tor, I
said that multiple requests were the problem. But pfg said:[0]

| AFAIK TBB doesn't create per-domain circuits for every subresource
| on a site (that would kill performance on many sites with 10s of
| third-party trackers, CDN hosts, etc.), but rather one circuit per
| "URL-bar domain". That domain doesn't change when a CloudFlare site
| renders reCAPTCHA.

Is that correct? And if so, why are CAPTCHAs so slow?

[0] https://news.ycombinator.com/item?id=11388560
-- 
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

