<html>
<head>
<style>
.sw_message P{margin:0px;padding:0px;}
.sw_message {FONT-SIZE: 12pt;FONT-FAMILY:Tahoma,Arial,Helvetica,sans-serif;background:white;}
.sw_message blockquote{margin-left:5px;padding-left:5px;border-left:2px solid #144fae;color: #144fae;}
.sw_message blockquote blockquote{border-left:2px solid #006312;color: #006312;}
.sw_message blockquote blockquote blockquote{border-left:2px solid #8e5656;color: #8e5656;}
.sw_message blockquote blockquote blockquote blockquote{border-left:2px solid #888;color: #888;}
</style>
</head>
<body class="sw_message">
<div>Reply to the email, say that you found a misconfiguration in your Tor <br>daemon which could have accounted for this problem and you've repaired <br>it, and hopefully this problem is resolved for the future.<br><br>Put the below as your exit policy in torrc, and I'd stop/start the <br>service to be sure it grabbed it.<br><br>Using the below exit policy, we've had our exit node running for a <br>couple months or so doing pretty good bandwidth, and not had a single <br>warez-related complaint. Seen some complaints about SQL injection <br>attacks but perhaps those will annoy your ISP less.<br><br>ExitPolicy accept *:20-23 # FTP, SSH, telnet<br>ExitPolicy accept *:43 # WHOIS<br>ExitPolicy accept *:53 # DNS<br>ExitPolicy accept *:79-81 # finger, HTTP<br>ExitPolicy accept *:88 # kerberos<br>ExitPolicy accept *:110 # POP3<br>ExitPolicy accept *:143 # IMAP<br>ExitPolicy accept *:194 # IRC<br>ExitPolicy accept *:220 # IMAP3<br>ExitPolicy accept *:389 # LDAP<br>ExitPolicy accept *:443 # HTTPS<br>ExitPolicy accept *:464 # kpasswd<br>ExitPolicy accept *:531 # IRC/AIM<br>ExitPolicy accept *:543-544 # Kerberos<br>ExitPolicy accept *:554 # RTSP<br>ExitPolicy accept *:563 # NNTP over SSL<br>ExitPolicy accept *:636 # LDAP over SSL<br>ExitPolicy accept *:706 # SILC<br>ExitPolicy accept *:749 # kerberos <br>ExitPolicy accept *:873 # rsync<br>ExitPolicy accept *:902-904 # VMware<br>ExitPolicy accept *:981 # Remote HTTPS management for firewall<br>ExitPolicy accept *:989-995 # FTP over SSL, Netnews etc<br>ExitPolicy accept *:1194 # OpenVPN<br>ExitPolicy accept *:1220 # QT Server Admin<br>ExitPolicy accept *:1293 # PKT-KRB-IPSec<br>ExitPolicy accept *:1500 # VLSI License Manager<br>ExitPolicy accept *:1533 # Sametime<br>ExitPolicy accept *:1677 # GroupWise<br>ExitPolicy accept *:1723 # PPTP<br>ExitPolicy accept *:1755 # RTSP<br>ExitPolicy accept *:1863 # MSNP<br>ExitPolicy accept *:2082 # Infowave Mobility Server<br>ExitPolicy accept *:2083 # Secure Radius Service (radsec)<br>ExitPolicy accept *:2086-2087 # GNUnet, ELI<br>ExitPolicy accept *:2095-2096 # NBX<br>ExitPolicy accept *:2102-2104 # Zephyr<br>ExitPolicy accept *:3128 # SQUID<br>ExitPolicy accept *:3389 # MS WBT<br>ExitPolicy accept *:3690 # SVN<br>ExitPolicy accept *:4321 # RWHOIS<br>ExitPolicy accept *:4643 # Virtuozzo<br>ExitPolicy accept *:5050 # MMCC<br>ExitPolicy accept *:5190 # ICQ<br>ExitPolicy accept *:5222-5223 # XMPP, XMPP over SSL<br>ExitPolicy accept *:5228 # Android Market<br>ExitPolicy accept *:5900 # VNC<br>ExitPolicy accept *:6660-6669 # IRC<br>ExitPolicy accept *:6679 # IRC SSL <br>ExitPolicy accept *:6697 # IRC SSL <br>ExitPolicy accept *:8000 # iRDMI<br>ExitPolicy accept *:8008 # HTTP alternate<br>ExitPolicy accept *:8074 # Gadu-Gadu<br>ExitPolicy accept *:8080 # HTTP Proxies<br>ExitPolicy accept *:8087-8088 # Simplify Media SPP Protocol, Radan HTTP<br>ExitPolicy accept *:8332-8333 # BitCoin<br>ExitPolicy accept *:8443 # PCsync HTTPS<br>ExitPolicy accept *:8888 # HTTP Proxies, NewsEDGE<br>ExitPolicy accept *:9418 # git<br>ExitPolicy accept *:9999 # distinct<br>ExitPolicy accept *:10000 # Network Data Management Protocol<br>ExitPolicy accept *:11371 # OpenPGP hkp (http keyserver protocol)<br>ExitPolicy accept *:12350 # Skype<br>ExitPolicy accept *:19294 # Google Voice TCP<br>ExitPolicy accept *:19638 # Ensim control panel<br>ExitPolicy accept *:23456 # Skype<br>ExitPolicy accept *:33033 # Skype<br>ExitPolicy reject *:*<br><br> </div><div> </div><div id="editor_signature"></div><div>On Thursday 24/10/2013 at 9:11 pm, Christopher Jones wrote: </div><blockquote type="cite"><div>I’ve been running an exit relay for about 3 days and, sure enough, some BitTorrent bugger caused <a target="_blank" href="http://sh3lls.net">sh3lls.net</a> to send me a DMCA nastygram:<div><br></div><div><blockquote><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">We have got the following complain, please remove all illegal torrents immediately from your server:</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Evidentiary Information</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Title: Suits (TV)</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Infringement Source: BitTorrent</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Initial Infringement Timestamp: 17 Oct 2013 22:06:17 GMT Recent Infringement Timestamp: 17 Oct 2013 22:06:17 GMT Infringing Filename: Suits Season 3 Episode 6 (The Other Time) (HDTV x264)-ASAP (1GBps SeedBox).mp4 URL if applicable: </span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Infringing File size: 364405400</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Infringers IP Address: 64.32.14.34</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Bay ID: 7fbb4256bfca558d5a809b9f6536b5fd5e4e782d|364405400</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(245, 245, 245);">Port ID: 33788</span></blockquote><br></div><div>I followed through with the templates provided by the Tor Project as a response to the DMCA takedown notification. A day later, the ISP sent me this:</div><div><br></div><div><blockquote><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(238, 246, 255);">Dear Christopher</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(238, 246, 255);">Whether you run Tor or not, we even told you in past, it's your responsibility to stop all abuse</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(238, 246, 255);">If Tor is causing it, stop the program Tor on your server, if we get another complain we will have to suspend/terminate your services</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(238, 246, 255);">tor always always gets lots and lots of abuse and complains</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(238, 246, 255);">Update us within 24 hours</span><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><br style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif;"><span style="color: rgb(102, 102, 102); font-family: 'Lucida Sans Unicode', 'Lucida Grande', sans-serif; background-color: rgb(238, 246, 255);">Thanks</span></blockquote><br></div><div>I was never provided with the full text of the original DMCA complaint, so I was unable to respond. Furthermore, I was never “even told…in the past” that I had to stop all abuse caused by Tor. Tor is not singled out in the ToS or AUP. And I was certainly never told anything in the past about abuse and Tor specifically. As I said, first warning. Then there’s the “tor always always gets lots and lots of abuse and complains [sic]”. Which is kind of bizarre, because their position on tor seems a bit cagey. Does the claim about lots of abuse mean they won’t allow exit nodes? Or is that just a “hint” that I’d be better off not trying to run it? </div><div><br></div><div>And this is an ISP I picked from the good list.</div><div><br></div><div>Suggestions are welcome. I’m running with the default exit node policy, which should block most of the abuse-laden ports. BitTorrent’s a little harder to deal with. I’ve no qualms working with the ISP to mitigate their concerns, but I’m not sensing their returning the same spirit of cooperation.</div><div><br></div><div>.cpj</div></div>_______________________________________________<br>tor-relays mailing list<br>tor-relays@lists.torproject.org<br><a target="_blank" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays</a><br><br></blockquote><br>
</body></html>