Delivery-Date: Mon, 22 Aug 2016 20:28:44 -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 0F72F1E0C15;
	Mon, 22 Aug 2016 20:28:42 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 87BCCE0751;
	Tue, 23 Aug 2016 00:28:30 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id CE379E06FB
 for <tor-talk@lists.torproject.org>; Tue, 23 Aug 2016 00:28:23 +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 g95sqZEw4Fcs for <tor-talk@lists.torproject.org>;
 Tue, 23 Aug 2016 00:28:23 +0000 (UTC)
X-Greylist: delayed 595 seconds by postgrey-1.35 at eugeni;
 Tue, 23 Aug 2016 00:28:23 UTC
Received: from turtles.fscked.org (ns531898.ip-149-56-25.net [149.56.25.211])
 (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 798A1E048A
 for <tor-talk@lists.torproject.org>; Tue, 23 Aug 2016 00:28:23 +0000 (UTC)
Date: Mon, 22 Aug 2016 17:19:57 -0700
From: Mike Perry <mikeperry@torproject.org>
To: tor-talk@lists.torproject.org
Message-ID: <20160823001957.GA24737@torproject.org>
References: <0F822E77-1D83-431E-A342-47D6FE4C6421@gmail.com>
MIME-Version: 1.0
In-Reply-To: <0F822E77-1D83-431E-A342-47D6FE4C6421@gmail.com>
Subject: Re: [tor-talk] sadly have to shut down my tor relay after less then
 24 hours
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
Content-Type: multipart/mixed; boundary="===============1734947100651183478=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============1734947100651183478==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK"
Content-Disposition: inline


--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Sarah Alawami:
> Hello to all. Sadly I have to shut down my tor relay after less then 24 h=
ours, as I received a copyright violation and I don't want any network rest=
rictions  placed on me as I want the 150mbps speed.
>=20
> Sorry to all who were using it, but yeah there it is.

Was this a DMCA takedown related to bittorrent traffic? When I ran an
exit, I had a lot of luck with this policy:
https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy

Basically restricting yourself to core internet services reduces the
chances that bittorrent clients choose a port from the policy. With a
1Gbit exit and that policy, I went from 60 DMCA notices a day down to 0
over the life of the exit (about 3 years).

Unless something new is happening? Did the complaint(s) give specifics
about the location and type of infringing content that was accessed?

More services are always better. I've been thinking about making that
policy into a torrc option, so it would be useful to know if the
situation has changed.

--=20
Mike Perry

--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXu5atAAoJEOI7sywPEpQCDzkQAMx40zSG7PZtsFWbfI0UiEgN
BMdpqu1ZxjB2Xb48q4zeedymV3cS5Itl8pwk2dFDtywXx+nNMnOdgH5yPx1RorHD
hub/bbeEjWbL4pXbBZ/QnR6/eNjCR8AAKPD8s6o2NZWlVhZLIqRmaFDtR7Sx5t8Z
d01I50KmjHOoWy3kSXzmUF7tmr3rT/cUv54WPqanSYOWt5wKFjOlfdw1PcUsDAHA
R/AHKe4nrEGhhF5JlgQgKatWTsDmQgw+vkQDFCbO/uu0eU6pRlAyfWfJbJjYNK4q
KaF1hNRHhC6zehxvtloUc1HlMZufyoKY7gfdOW3kIRsuNrpQKOploR2H4dIXutSJ
LEY9Ohosy+GUogCefUt+YbZbDgJCFM7cHw5WHvURnVtUuRhQQvRFgTEOUFpB87fX
IAbnTtOi9byFS4HNsvhJvtsO+HJ4tOMXFnZNsR1+qyISbfw+T+DTXPALfD7l+P3f
tjeVZ7fbHwipwoIzOy1VXHd0h0EPsHnSpeldgGfmzSmlkYt8tRo2WwekF4YdbXoy
OxRe9jBNb6y3zXKD0NrtThcEhHmhcf+JVN+cbK4QObCh7kXV6GjP9/y/SANdAtld
Tu32Zu+6hSG9QDO4f/jxxTd1BGWrD1Xm4vh2V4PmCl70kn3cPV/Sr9SVeLiJvMMY
hchGKWn6QH4H68N3mPGD
=SLS6
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--

--===============1734947100651183478==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCnRvci10YWxrIG1haWxpbmcgbGlzdCAtIHRvci10YWxrQGxpc3RzLnRvcnByb2plY3Qub3Jn
ClRvIHVuc3Vic2NyaWJlIG9yIGNoYW5nZSBvdGhlciBzZXR0aW5ncyBnbyB0bwpodHRwczovL2xp
c3RzLnRvcnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby90b3ItdGFsawo=

--===============1734947100651183478==--

