Delivery-Date: Thu, 31 Mar 2016 12:27:43 -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=-3.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_LOCAL_NOVOWEL,RCVD_IN_DNSWL_MED,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 85D511E08B9;
	Thu, 31 Mar 2016 12:27:41 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9D195383B0;
	Thu, 31 Mar 2016 16:27:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A69F5383B0
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 16:27:33 +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 ojNwDI5o0YVQ for <tor-talk@lists.torproject.org>;
 Thu, 31 Mar 2016 16:27:33 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 380F920EE9
 for <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 16:27:32 +0000 (UTC)
Received: from [192.168.2.60] ([99.190.181.188]) by mail.gmx.com (mrgmx001)
 with ESMTPSA (Nemesis) id 0M0QAP-1ZrLlV01aH-00ubRn for
 <tor-talk@lists.torproject.org>; Thu, 31 Mar 2016 18:27:28 +0200
To: tor-talk@lists.torproject.org
References: <20160330132105.GA8024@lapsedordinary.net>
 <20160330150151.GD3164@riseup.net> <56FC34BD.9070808@gmx.com>
 <20160331052504.GA13693@inner.h.apk.li>
From: Joe Btfsplk <joebtfsplk@gmx.com>
Message-ID: <56FD4FEC.1040903@gmx.com>
Date: Thu, 31 Mar 2016 11:27:24 -0500
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <20160331052504.GA13693@inner.h.apk.li>
X-Provags-ID: V03:K0:od3qtUjMJ4QtZKwn5tWBsO/j5DHgDP5pSOBshLATs5ZnTkcJWNA
 8Ewr+c5jm3IYABaMfp+QK6K6ag7Kir2ukK+myY9W6h+Rk7e3lk6taQ2EAASixxKKGHorz+Q
 uf5GyBmNqV7zb8uVqpWGxAh2gQ4AhWYcgtWAc+CbWOlJsom7X3kqeKNESVMfdffe1BTSQdc
 LHKhqCo5trByl8gh7hngQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:8CLvSeFPISU=:WEca133ZLPfdAHJzAbqadR
 mpsPMYjML2rMbHPWBHsl2xfm1TWXQMFLWmbwuhlrxDitd0lNGzMUPJ9ws0/Z9ODH88cCJn+yd
 RyOw7RklW/rvmw0cuWLX/oXwawtv3XmrpsGVy24rm6sfWeYAO2CIJi+11aDYb6g8PNX/Jx/CZ
 xU7QdNhRYQxdHEpecTS2EUQ3V1GmJyl7BehbBTBQ6TpdxK6+QD02dfWJVNCDj9jRneXwY/q24
 ZF6+TSb6Hzb71KTSS6AWFlxqz7MBPLxO12jyHMlCKNIRuCMBvutJdatmUYPAGAeVvP4HvHZsz
 tL8Ogo8xfEc4zueBLfRzG1TqXTIBQ1z4oXKU716tuAkovNNPr+dTBGCcnPSVOFTMFr3JjXJ77
 Q+/tGicvTgAkB74FSb0hnZNfG1D9zHiyTLXKAWmsCB9AVmicTOoC14Z1e1R/LHU6711tOkquB
 pkNMfappB3LRyoGaq9yvJ78gDSFtq9FaEWopSb5bMZTpTwBosE/DWzy78lw7sV+qPnSaAizgm
 PWje6GhKue3fCEs8ZW7YSz8hrw79JGW8uIiX3+hYmaKrAJnRSraltNNqoB8ahuOEpRFEHyEA9
 9/dvqdohnnTxSUuK+6/9DOuixJUtiyaFypAyV+Jbxqkf8PSxsNR6O2chw0PDt0rhLzN9EtK59
 EK6186IXqg36k4PzsO+5RPw7AiiayBc9dgaW1hyxZeAh0ew/IXCrMjwE6GPvTeLk4Y3CDDJz1
 zVaJ75qYkADaRybdz2wxh6xOJ2O4lonNEu6rh/izEd6xsA5pyEHaV0c8oyFmcUXbwaE6ufiWA
 /QigcOn
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 3/31/2016 12:25 AM, Andreas Krey wrote:
> On Wed, 30 Mar 2016 15:19:09 +0000, Joe Btfsplk wrote:
> ...
>> At times, Cloudflare or some sites may say, "Gee, whiz - we're not
>> blocking TBB intentionally.  We're working on a solution."
>> But I don't buy that  100%.  It's possibly just a politically correct
>> excuse vs. saying, "We can't track you around the globe / make $, so we
>> don't want you taking up bandwidth or other resources (like site tech
>> support, etc.).
> It would be quite a lot of effort to do that this way, especially since
> the (preliminary) outcome is the same - sorry, it won't work any better.
>
> What I wonder is how they want to make a difference using .onion addresses
> for their customers - tor crawlers can take that redirect just so.
Andreas, sorry - don't understand part of your comment.
"It would be quite a lot of effort to do... *what?*... this way... - 
sorry, it won't work any better."
Are you saying they it's a lot of effort for them to block Tor / TBB?  
Or any browser - with any particular addons / plugins, settings, for 
that matter?  I'm no expert, but IIUC, it'd be very simple.
Just script,  If Browser=TorBrowser, then captcha response = 
"incorrect."  Or TBB users must enter correct captcha a minimum of X 
times before accepting, etc.
>> And for all the other sites that don't use Cloudflare (or other
>> unsolvable captchas), but don't block TBB, if _"90+% of all Tor traffic
>> attempts something malicious_," then how in the world do all those sites
>> stay in  business / stay up & running?
> 90% of tor traffic isn't 90% of total traffic.
True.  Neither CloudFlare CEO nor I said it was.  He said, " ... "94% of 
requests that we see across the Tor network are _per se_ malicious," 
(what ever he means) w/o backing up the statement.
Again, if what CloudFlare CEO said is true, I don't see how other sites 
not using thier captchas & blocking Tor, keep running.
I've seen Cloudflare on low value target sites, like wood screw mfg info 
sites & similar.  Unless other screw mfgs are sabotaging them, I doubt 
much malicious activity is directed at such sites.

94% is saying essentially ALL Tor traffic / requests are "per se" 
malicious or use inordinate amt of resources.  That leaves me & 6% of 
users that aren't.
Maybe ? he's counting crawler *individual* requests - page by page - as 
malicious?  They might make many more requests than real users, thus the 
94% claim?

His statement(s) & reasoning about blocking Tor still seem strange.  As 
they say, "follow the money trail."  "Money trumps all other reasons / 
motives."
I still say trackers aren't going to pay sites for TBB traffic. Don't 
say, "You're using Tor - get lost" - bad for public relations.  Instead, 
play dumb & covertly discourage (some) Tor users  - so they access the 
site w/ unhardened browsers.

Can't sites tell the difference in actions of crawlers & real users?
I'm sure some use browsers other than TBB for crawling & malicious 
activity.  Can't sites block / time-out crawlers from continuing to 
access entire site, once it becomes apparent - regardless of which browser?

I get "time outs" from making 2 very narrow term searches in < 2 min. or 
so, on some sites I'm registered on & participated - for a long time.
Why can't sites do the same w/ crawlers' rapid, repeated requests?

>   Also, e.g. those sites
> will just see that the email addresses they publish are getting spammed,
> but they won't even make the connection to crawling via tor.
>
Don't get the connection between this & the issue of Tor being blocked 
by Cloudflare.
-- 
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

