Delivery-Date: Thu, 23 Jun 2016 14:05:51 -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 [138.201.14.202])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 5B5AB1E004D;
	Thu, 23 Jun 2016 14:05:49 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 976BCE08A4;
	Thu, 23 Jun 2016 18:05:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C3030E0881
 for <tor-talk@lists.torproject.org>; Thu, 23 Jun 2016 18:05:29 +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 LUGmPHAsf85N for <tor-talk@lists.torproject.org>;
 Thu, 23 Jun 2016 18:05:29 +0000 (UTC)
X-Greylist: delayed 341 seconds by postgrey-1.35 at eugeni;
 Thu, 23 Jun 2016 18:05:29 UTC
Received: from hv1.intersafeit.com (hv1.intersafeit.com [50.115.119.68])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 38AB1E086A
 for <tor-talk@lists.torproject.org>; Thu, 23 Jun 2016 18:05:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by hv1.intersafeit.com (Postfix) with ESMTP id 923002C0
 for <tor-talk@lists.torproject.org>; Thu, 23 Jun 2016 11:59:43 -0600 (MDT)
X-Virus-Scanned: Debian amavisd-new at hv1.intersafeit.com
Received: from hv1.intersafeit.com ([127.0.0.1])
 by localhost (mail.intersafeit.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id bg2bgdz3_Gak for <tor-talk@lists.torproject.org>;
 Thu, 23 Jun 2016 11:59:43 -0600 (MDT)
Received: from [10.119.75.218] (unknown [193.104.113.41])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by hv1.intersafeit.com (Postfix) with ESMTPSA id 945C690
 for <tor-talk@lists.torproject.org>; Thu, 23 Jun 2016 11:59:42 -0600 (MDT)
From: tor <tor@0xf00.guru>
To: tor-talk@lists.torproject.org
Message-ID: <576C238C.6040605@0xf00.guru>
Date: Thu, 23 Jun 2016 11:59:40 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.8.0
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------090509000905040402020004"
X-Content-Filtered-By: Mailman/MimeDel 2.1.18
Subject: [tor-talk] Attack through tor bad for all
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.18
Precedence: list
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>
Reply-To: tor-talk@lists.torproject.org
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

This is a multi-part message in MIME format.
--------------090509000905040402020004
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Sadly, an attack run through tor destined for a uk2 hosting provider is
being met with a null routes for exit nodes under a policy of "wont' be
lifting it any time soon". The group owns several brands spanning data
centers in a variety of areas and continents. Although not super eager
about allowing tor exit nodes on their networks the group and it's
brands have allowed them so long as DMCA volume isn't a problem. Some
operators have limited those issues via exit policies to certain ports.

As everybody knows, the problem with running the attack through tor is,
aside from being ineffective in the long run, endangering the viability
of hosting exits on their networks as well as accessing content hosted
on their networks from tor. This threat is not new news but I wish to
point it out this method is probably not resolving your grievances and
it's problematic for those who are otherwise unaffiliated with your
actions. Many network providers are in this situation where abuse
through tor ends up hurting the tor community by limiting where exits
can exist and what content on their networks can be seen through tor.

To the initiator of the traffic which they are not receiving any more, I
hope you find a way to resolve your beef without harming the network
that you depend upon. I'm sorry you feel this is your best option and I
hope that when this is over that their sizable client base isn't totally
dark to tor. It would be nice to be able to utilize their geographically
diverse networks for precious exit nodes that we all benefit from. I'd
like to help find a better option for everyone involved.

My public key attached and also on pgp.mit.edu:
https://pgp.mit.edu/pks/lookup?search=tor%400xf00.guru&op=index


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXbCOKAAoJELyL0KWU6P5v1PcH/0P1YX07ljdNKbAId7KUHpNo
192bK7L7BW1rP5ppTOnFKBpdwtXZMHxzVhpUgP159BYdawiiLayB8DmL68073v6D
9O6xPLXhl1AlXay1g2DAUgS76Uv1Q0U++kOUi40qYINiktwN66rLOksYQkaLvj6Z
IPl/Pwq0bpr61/e5sTWT/0SsceRSNVuWbozWJkPLGOU14wp0MhykwV51ESAM1jHh
ChNaFM/c/u4tmI4QBoq5fEVBQrysahJy5tsSyngEEoeG3uhTINKZaHR+lHf682YX
Sfl8jZy7ZDKkLuilw1acieJD9uKOqz93VPKb47F3wChbHWSy0bpJg0qZpE0+HIE=
=DFbQ
-----END PGP SIGNATURE-----

--------------090509000905040402020004
Content-Type: application/pgp-signature;
 name="0x94E8FE6F.asc.sig"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="0x94E8FE6F.asc.sig"

iQEcBAABCAAGBQJXbCOMAAoJELyL0KWU6P5vyN0H/jYKm3KGwyW+ngRtludOWh/eqhyuJmF/
5UxzdEqJWKCmbPK/qcLKz0tIN9rgMAn2ARcinS9X+z8/QbDmigpEmba3JDv/Ur2v4E+rtNOb
T5RbL0sYQgPxCiy5GW9HzvAKRfshBQiMZrcbJzemEOAG7h4+H6OkSx9IdcCsFqf5iJmbkq/P
PxK+CzscWsCAthJH4nf49083Q5OzUrPfirodPMoetlcg0KGd+rTAcenD8vVBuEWNJhliTH8x
kZ7iAKeeRQhLAMvTsHLW42wTTV3jDYFbRGUuQ40qdV84UPN8Bj/YphT3RCEXR48E/hQHAVNy
nKzlfIN7KVyxf3dWWnMzi/I=
--------------090509000905040402020004
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCnRvci10YWxrIG1haWxpbmcgbGlzdCAtIHRvci10YWxrQGxpc3RzLnRvcnByb2plY3Qub3Jn
ClRvIHVuc3Vic2NyaWJlIG9yIGNoYW5nZSBvdGhlciBzZXR0aW5ncyBnbyB0bwpodHRwczovL2xp
c3RzLnRvcnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby90b3ItdGFsawo=

--------------090509000905040402020004--

