Slashdot Mirror
Courts Force Danish ISP to Block Torrent Tracker
Pirate writes "A Danish court ruled in favor of the IFPI, and ordered the Danish ISP Tele2 to block all access to the popular BitTorrent tracker. The Pirate Bay, currently ranked 28th in the list of most visited sites in Denmark, is working on countermeasures."
"It's very frightening that IFPI can get through the courts with something like this. In Turkey and China its the state that decides what information the people can access and what should be censored. In Denmark its apparently the record industry,"
I think that sums it up quite nicely.
Copyright 2010. All rights reserved. This comment may not be copied in any way including, but not limited to caching.
I always wondered why folks didn't use other Internet technologies such as DNS to get around the "blocking" issue?
What's to prevent all the tracker information from being put into a master DNS server with a low TTL, and building up torrent search software which queries DNS?
You could store this into TXT records and query DNS to find the results;
"Thomas-Edison-The-Lost-Chord-1888" IN TXT a9cd93da939d9c9
The TXT being a unique code which again is looked up in DNS
a9cd93da939d9c9.subdomain.domain.toplevel
And the result is a list of IP's that are currently seeding the torrent,
and thus BT can subscribe to. I can do a dynamic DNS update to
add my client to the list of machines seeding the torrent.
So there is no HTTP traffic involved in this exchange. The DNS is
typically provided by the ISP, so caching would be in effect. So
you want TTLs to be low. The clients will be querying against the ISP's
DNS server. Dynamic DNS would be to the parent DNS server. The ISP could
blackhole the zone by putting in a dummy record, but that can be overcome
by using the root DNS servers or using any of the many open DNS servers.
Anyway, my thoughts on the subject. ICMP would be another protocol one could
potentially use to get around this too.