Need help with MPAA threats

[David Kammering]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hannah Schroeter schrieb:

>> After all, a running Exitnode relaying on the "standard" ports like HTTP
>> seems to be (for me) better than a completely switched off node because
>> of legal troubles regarding file sharing.

> But in the end, the situation is all the same for HTTP(S) as for BT. BT
> can (and *is*) used for legal content. E.g. I've already pulled (and
> redistributed, i.e. contributed) OpenBSD *legally* via bittorrent (of
> course not via tor). OTOH, you can use http(s) for illegal content, too.
> Especially via ssl.

I agree that there are some legal uses of BT but most of the shared
stuff is copyrighted material IMHO. Surely you can use other protocols
for illegal stuff and its perfectly ok with me to relay such traffic.
The problem with P2P via Tor is that the exit nodes' ip will show up in
the MPAA's logs and they will (automated) harrass you (or worse) your
provider with their DMCA bs. I don't really care if I have to answer
such letters over and over again but my server provider will probably
get sick in forwarding them to me and may take down the server.


> And, if I see things right, the bandwidth argument doesn't compute.
> IIRC, only the client<->tracker traffic is relayed via tor, and that's
> not the mass traffic of the actual big files.

Hmm, I must admit that I'm not too deep into p2p via Tor, but what I
noticed from my mrtg stats of the exit node is that running a more
restrictive exit policy gives me typical traffic flows with some spikes
and so on; reverting to the standard policy peaks out the bandwith
completely. I have no further checked what is the cause of this as it
would have involved logging traffic but I think most of it is p2p
traffic as running on the restrictive exit policy got me no further
notes from the MPAA.

Actually it is an observation I already thought about asking on the
list, maybe someone could clarify if it is really p2p traffic peaking
out the link with the open exit policy?

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

iD8DBQFJRlePVAJHIfCS0zQRAiB4AKCfQinXC+S/mffQaR28FcR15W4ryQCghJRz
VMSGde5Z55x8DJ3s8dcFgZo=
=KlJS
-----END PGP SIGNATURE-----