Delivery-Date: Wed, 27 Jan 2016 03:45:15 -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=-4.2 required=5.0 tests=BAYES_00,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 76B841E00C2;
	Wed, 27 Jan 2016 03:45:13 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5D2DD38D55;
	Wed, 27 Jan 2016 08:45:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BE66C38D3D
 for <tor-talk@lists.torproject.org>; Wed, 27 Jan 2016 08:45:03 +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 cW5ugW6nE5nz for <tor-talk@lists.torproject.org>;
 Wed, 27 Jan 2016 08:45:03 +0000 (UTC)
Received: from mail-lf0-f100.google.com (mail-lf0-f100.google.com
 [209.85.215.100])
 (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 5E28D38D4B
 for <tor-talk@lists.torproject.org>; Wed, 27 Jan 2016 08:45:02 +0000 (UTC)
Received: by mail-lf0-f100.google.com with SMTP id n70so132016lfn.2
 for <tor-talk@lists.torproject.org>; Wed, 27 Jan 2016 00:45:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:from:message-id:date
 :user-agent:in-reply-to:content-type:content-transfer-encoding;
 bh=TUBHittLu9QJ8O4Z7127bwtJ40JTZAlvjzQA4ksP97w=;
 b=Vs/FlGvHd65TnsibcTR1y7SMYu37IZG0W6e+nnyXcyFCRHg3lTcfLM4oesTfN0nkqp
 PFFnlFigxPfKdRqhd9vkjvO6jtbM7P+m53ArFMstIDuzc1H5bxAK1pmV0g14sAVzJ3QF
 PZ/7TKO/iX2XHGOt4KrQimkNQfnAUB1iDVr44/DGyfBJrtCvSSxoxFZrppYGXUvsjX9h
 jMKHlhnpaJbruYGhzh+xmRYQOnfZu/HDpMYyg2rxLVbGwDlY3Us0eZC6WJKeRLAvKO9H
 YgI5ahCWb4KgxwiuCWAhC6fjLHbtFYHY1zDtxulmPhIgE/9e7OogEORPbOUAGO2MRy9h
 TO/g==
X-Gm-Message-State: AG10YOQmYcFrYpwZQ9JueQDOUEjh+40XZdySgg4mFj6KglhATLAVDOl4j/1YPPvvkkSy4ZlseXDDPB0Cko9cGQbe9kULU3xN
X-Received: by 10.28.16.8 with SMTP id 8mr30872083wmq.77.1453884299684;
 Wed, 27 Jan 2016 00:44:59 -0800 (PST)
Received: from apps.globaleaks.org (demo.globaleaks.org. [194.150.168.64])
 by smtp-relay.gmail.com with ESMTPS id gl10sm423459wjd.0.2016.01.27.00.44.59
 for <tor-talk@lists.torproject.org>
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Wed, 27 Jan 2016 00:44:59 -0800 (PST)
X-Relaying-Domain: apps.globaleaks.org
To: tor-talk@lists.torproject.org
References: <1484141453752577@web9h.yandex.ru> <20160126095831.GA28447@alarmpi>
From: "Fabio Pietrosanti (naif) - lists" <lists@infosecurity.ch>
X-Enigmail-Draft-Status: N1110
Message-ID: <56A88383.6030309@infosecurity.ch>
Date: Wed, 27 Jan 2016 09:44:51 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.5.1
In-Reply-To: <20160126095831.GA28447@alarmpi>
Subject: Re: [tor-talk] A multi-layer proof of work system to solve the
 Tor/CloudFlare problem?
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>
MIME-Version: 1.0
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 1/26/16 10:58 AM, Pickfire wrote:
> On Mon, Jan 25, 2016 at 09:09:37PM +0100, Cain Ungothep wrote:
>>> That way a normal web client, normally browsing a website, would not be
>>> impacted from end-user experience, but any automated system (the ones
>>> causing
>>> problems to Cloudflare)
>>
>> Why can't people separate Tor from Tor Browser in their minds?  Tor is a
>> network transport.  Not all Tor users are lusers sitting behind Tor
>> Browser,
>> clicking things.
> 
> Nice speech, I don't use Tor browser, I use Tor for almost every
> application. I would like to automate a link checker for it, but the
> useless Cloudflare broke my script to check broken links.

At first Tor is mostly used by Tor Browser, it's probably a marginal
part of users that use Tor without Tor Browsers.

By the way whatever you are using for server-side script automation, a
Javascript interpreter with server-side node.js or other JS interpreter
used from other languages, can replicate exact JS-Pow functionality
possibly implemented by CloudFlare and executed by Tor Browser.

It doesn't change anything w.t.r. to the problem that need to be
addressed and that this idea would propose to address, that's a
fundamentally different approach trying to identify an automated way to
fight against automated scanners.

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

