Delivery-Date: Mon, 12 Oct 2015 20:00:28 -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.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 5A9231E011F;
	Mon, 12 Oct 2015 20:00:26 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C5E0D380C3;
	Tue, 13 Oct 2015 00:00:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 38CF938092
 for <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 00:00:14 +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 z8nuJ3Uj6QWs for <tor-talk@lists.torproject.org>;
 Tue, 13 Oct 2015 00:00:14 +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 17022380CC
 for <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 00:00:12 +0000 (UTC)
Received: from localhost ([77.247.181.163]) by mail.gmx.com (mrgmx003) with
 ESMTPSA (Nemesis) id 0MVMgI-1a51GQ1N8w-00YmAp for
 <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 02:00:08 +0200
Date: Tue, 13 Oct 2015 01:59:24 +0200
From: "sh-expires-12-2015@quantentunnel.de"
 <sh-expires-12-2015@quantentunnel.de>
To: tor-talk@lists.torproject.org
Message-ID: <20151012235924.GB2119@localhost.localdomain>
References: <55FA9165.5010909@gmail.com>
 <CAD2Ti2-cm3pqdz-DWNstgy3LHMoNs__f_YMobjLZHDreqvbQFQ@mail.gmail.com>
 <55FB38C6.8050503@gmail.com> <5614417C.9060108@gmail.com>
 <20151009004937.GD30048@localhost.localdomain>
 <5617F3C4.9000201@gmail.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <5617F3C4.9000201@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Provags-ID: V03:K0:Ms1oCmvweUzQDPBnQRViBhy7Zk375yMHizZFaq4oiklqG04jBgv
 A3CcpnUr/q46XqZUcxSJ9ssYr91Nss1YZGBfQsT3M102s82ZGnWZgSMGb60izvGAGyoZCfI
 qZywGpOcMLKUblxY8rwTTU2+xP76yYOdDIR8Gw1A41UE5kdaZmaZtC7UwpaPqK44R7vOLnL
 A56lfk+zwxpfv0CESEpnA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:uz6f6Ylum60=:jzOMiDq7+22EaemMKiwXCL
 RZNJRG07Ky3zI/OkBB4Yhw5FvMN5UEaaZnUvc1wdQaXLKFPoOCO+PKvzeeKCtCCLep1nRIOLw
 IiDihyXsvzbE4vah3URxoljFz5OHpn/pgBxYl5w6s9tZCk2FhWpSOQwr6PVq7rYKRre5EOOMs
 uSYTdjy93eOg8ntgryAPVahX6KWllAKKnzYMA3hcUZbR51hl9ZGbudel/eo/ESn10zjAr29le
 4cZuH2Sg9KeFc96pWx8/XERMBuMEeBFzZCXuh10KdMmx+YS/momHlNQQvpxyFqQ3tN1z9O0TY
 wNUfjd1nv6gxuSXSwncPZj76IOhUv6vKLqUOqAb3arY02g1D5iHvKBIP2rTijF4IZaBck6u/h
 ahqK6xH6G6bZfRF7bA5MHo5APw8mo1gvhWh8vckEjD9KTMXGiW7gLxKnJ/64KfLG/OByRmZJ6
 RpJvdebWC3Ep2nNueCrDFrLYQQNDD1758wu5TwVpGKi9E/or/Q+SpTKDlYBndT4Ohtz4aQ2cv
 3sIgTfBlbKgH4nTgEynULa+XWOtTIR2Yc1C6nYTOIGGksY+zjdgHZhGVMVl9QnoJgpa9Ztxbg
 /6bFu1kUWnGdBZOko9mFO8wL24oewva0RbHAeqUbWb0vZIc2MX8xbvNoRtcII+X5rlFuO2Knh
 O7pZAA4cC8OJR4qmyMjjueEmfg4/QA7ESIvt/CMLn3GUYXjyxM1RVxZ/Hr6tGHMMEmZ+R/aUl
 IxZaAZnoCC62/i5roSX7PRYlGucGWXn7LUtIOAT3PBK6YfmmUI9x2lIbZ5UeatG5ggEpYSFX3
 z8e3APW
Subject: Re: [tor-talk] Torrents real-time and dynamic blocklist
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 Fri, Oct 09, 2015 at 07:05:08PM +0200, Aymeric Vitte wrote:
> Anyway I don't think that's really of the interest of this list except
> that some exit nodes operators might envision to use something like the
> dynamic blocklist, if some are often bothered by notices/letters we can
> propose a trial to see if the list is adapted, which we think it is.

You are pretty right, your information isn't useful for anyone at all,
why would a operator of a exitnode allow a third party to control
his exit policy? Even partly, bad idea.

If and exit gets staturated by such traffic, it can reject
the default ports, like 6881 and the like, and Port-Ranges > 50.000,
that will provide much better results.

He could reject much more, without limiting usability of Tor.

If the few torrent-tracker operators would understand, that not
being able to scrape their trackers from a exit node is beneficary
for them too, we actually could achieve something here.

Anyway, given the distributed approach, protocols like BitTorrent, your
blacklist can only provide a false sense of security (the best case).
The problems, like being flooded by an adversary, I have addressed in 
the previous posting. ;)

My coworkers and I call such services, either a racket or snakeoil.

The problem, of being held accountable for torrenting are much better
addressed by using a VPN. Since the law is different for most of
the pariticipants of this list, in some countries you can still download
without any problems, problematic is uploading (distributing) stuff
other than your own, or wich is covered by libre licenses.

If you, wrongly, got held accountable, ask the lawyer form rightscorp,
if their network services are secured against routing attacks, and how they
tend to proof that the origin is really you out of your network, that
hasn't such measures (like sourceroute verification).

If you still want to throw money, throw it either at your local tor-
organisation, the tor-project or the folks producing a libre torrentclient.

Sorry, for giving you the impression, that I may address you Ayms, I am
adressing all the other people, that may consider your approach of a
centralized entity (blacklist) for clients using protocols or networks
like BitTorrent or Tor, that are somehow distributed.

I don't see peersm adressing any r/l issues, that are adressed by other
approaches at all.

P.S: This list needs a policy for advertisng paid services, like
$1 per distributed message paybale to the torproject ;)
-- 
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

