Delivery-Date: Tue, 13 Oct 2015 02:46: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.3 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RCVD_IN_SORBS_WEB,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 B7D791E13DA;
	Tue, 13 Oct 2015 02:46:41 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 5985C37EE3;
	Tue, 13 Oct 2015 06:46:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AB05A37D98
 for <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 06:46:30 +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 lV6ivuS1_H4z for <tor-talk@lists.torproject.org>;
 Tue, 13 Oct 2015 06:46:30 +0000 (UTC)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com
 [IPv6:2a00:1450:400c:c05::236])
 (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 610E437C70
 for <tor-talk@lists.torproject.org>; Tue, 13 Oct 2015 06:46:30 +0000 (UTC)
Received: by wicgb1 with SMTP id gb1so75503031wic.1
 for <tor-talk@lists.torproject.org>; Mon, 12 Oct 2015 23:46:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-type:content-transfer-encoding;
 bh=YjR6JXD9YIXTWksMU/pcz5kyt9qYJk5lq9/y0uyIDYo=;
 b=tsuFbcnb05jMT06zHeRmS+7Ot7q/IjClJgi4G+lA9r62MrgFJElHdv6RB07Bq859kE
 QfLTDOq7OjHQ0OepdSg77r87mvPpWm8RyF2YazENz6Uwr0FPc6fwKDapSXjwikRBEWJB
 bO+L4rgJaEcOVDj5ypu8PRFxnSydCghpTZBGsVMXDm3m26oou2jrJ/rDA+hLKRk91fyW
 WOdXZdJIxWEZhaPNWQ4dqqAc/HyZUbpiYbAyQuSr8dLE1CcJFLFEoeMdrx5SPv8AyFkP
 tAU3LYyv4Hd0BiDO3vMDf9/tl72b87yGILw+zblVKbPJSx68q76mH0dOuWVm9N3mUZd2
 hR+Q==
X-Received: by 10.194.114.133 with SMTP id jg5mr33199181wjb.98.1444718787482; 
 Mon, 12 Oct 2015 23:46:27 -0700 (PDT)
Received: from [172.19.123.88] ([147.67.241.226])
 by smtp.googlemail.com with ESMTPSA id i10sm1635512wjz.41.2015.10.12.23.46.26
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Mon, 12 Oct 2015 23:46:26 -0700 (PDT)
To: tor-talk@lists.torproject.org
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>
 <20151012235924.GB2119@localhost.localdomain>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <561CA8CE.5020204@gmail.com>
Date: Tue, 13 Oct 2015 08:46:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:38.0) Gecko/20100101
 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <20151012235924.GB2119@localhost.localdomain>
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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Well, please read the study and comments from others before posting, =

some had the same "doubts" and "snake oil"/"paying" concerns =

(torrent-live is open source and you can build your blocklist free of =

charge), they are addressed there

Does it happen that exit nodes get notices? Yes

We are not talking about port 6881 or > 50000, we are talking about =

dynamically blocking TCP connections to bt dangerous spies

And no, the method can not be fooled/flooded like this

Le 13/10/2015 01:59, sh-expires-12-2015@quantentunnel.de a =E9crit :
> 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 th=
ey
> 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 torrentclien=
t.
>
> 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 ;)

-- =

Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms

-- =

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

