Re: Need help with MPAA threats

[Curious Kid <letsshareinformation@xxxxxxxxx>]

Industry organization putting pressure on Tor exit node operators to filter leads to chilling effects.

As nodes start to filter, that traffic will seek out non-filtering exits. That would work like a funnel, as a majority of traffic of that sort will exit through a decreasing number of exits, thereby making those non-filtering nodes appear to be large-scale violators.

Has it occured to any of you that these organizations are being conspiciously aggressive with certain people with the complete knowledge that they are Tor exit node operators and what their exit policies are? They want complete network filtering, and that includes the Tor network.



----- Original Message ----
> From: David Kammering <david.kammering@xxxxxxxxxxxxxxx>
> To: or-talk@xxxxxxxxxxxxx
> Sent: Saturday, December 13, 2008 9:30:18 PM
> Subject: Re: Need help with MPAA threats
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Matthew McCabe schrieb:
> 
> > Here is where I need your help.  First, is there a good way to filter
> > out torrents in my exit policy?
> 
> I tried out some different exit policies after getting a big load of
> DMCA notices. My provider didn't really mind forwarding them to me but
> it got me started playing with the exit policies as I don't see any
> reason for me donating (expensive) bandwith for filesharing over Tor. I
> am currently running the exit policy pasted below on my exit node:
> 
> ExitPolicy accept *:20-23       # FTP,SSH,TELNET
> ExitPolicy accept *:53          # DNS
> ExitPolicy accept *:80-82       # HTTP
> ExitPolicy accept *:110-119     # POP3/NNTP
> ExitPolicy accept *:143         # IMAP
> ExitPolicy accept *:443         # HTTPS
> ExitPolicy accept *:465         # MAIL
> ExitPolicy accept *:587         # MAIL
> ExitPolicy accept *:993         # IMAPS
> ExitPolicy accept *:1194        # OPENVPN
> ExitPolicy accept *:1720        # H.323
> ExitPolicy accept *:1731        # Netmeeting Audio Control
> ExitPolicy accept *:5050-5061   # YAHOO MESSENGER, SIP
> ExitPolicy accept *:5190        # ICQ
> ExitPolicy accept *:5222-5223   # JABBER
> ExitPolicy accept *:3128        # Proxy
> ExitPolicy accept *:8080        # Proxy
> ExitPolicy reject *:*           # Disallow everything else
> 
> I think most needed protocols are included but I got my copyright
> infringements down to zero.
> 
> Maybe redefining your policy would anticipate further problems with your
> provider but still keep your exit node quite useful to most of the users.
> 
> YT,
> David
> 
> 
> - --
> GPG Key Fingerprint: C132 0FA2 C1C9 B5DA 5317 2D89 5402 4721 F092 D334
> Key ID: 0xF092D334
> Encrypted mails STRONGLY preferred.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFJRBtaVAJHIfCS0zQRAkpIAKC14SI8mxvYEl8Nb7HHZxoqYnnbjACfeTQq
> 3DcoCbzeQgZw4N2f+MCMCGc=
> =Zvi4
> -----END PGP SIGNATURE-----