Slashdot Mirror

← Back to Stories (view on slashdot.org)

Belgian ISP Forced To Block P2P Traffic

Posted by kdawson on from the it-could-happen-here dept.

An anonymous reader lets us know of developments in a case in Belgium that has been under litigation since 2004. The Belgian copyright watchdog SABAM has forced an ISP to begin filtering P2P traffic (PDF). According to the PDF on the SABAM site: "The Belgian Society of Authors, Composers and Publishers (SABAM) has just won an important legal battle within the context of the dispute that opposes it to the Internet Service Provider (ISP) Tiscali, which has become Scarlet Extended Ltd. In its sentence of June 29, 2007, the Court of First Instance of Brussels is demanding from the access provider that it adopts one of the technical measures put forward by the expert in order to prevent Internet users from illegally downloading SABAM's musical repertoire via P2P software." The rumor is that Scarlet will be forced to deploy the same software as MySpace uses (Audible Magic) to filter illegal P2P traffic from the legal.

4 of 207 comments (clear)

  1. A simple way to defeat this by bunburyist · · Score: 5, Informative

    I think that our Belgian friends could simply bypass this using protocol encryption for bitorrent. Since bittorrent can work on any port, portblocking filters are useless. Packet sniffers would have a tough time detecting encrypted traffic. The major bittorrent clients all support protocol encryption. For a guide on how to get it working with your client check out:
    TorrentFreak's guide to protocol encrpytion

    1. Re:A simple way to defeat this by Opportunist · · Score: 4, Informative

      It's one thing to outlaw something. It's another to enforce it. Or, in this case, it's easy to say "no P2P encryption allowed". But what is "P2P traffic"? A packet, having a valid HTTP header, trying to connect to a machine on port 0x50 is, usually, a request to a HTTP Server. It's easy, though, to use HTTP as a wrapper for any kind of traffic. Dunno if providers would be that happy about that, considering the incredible overhead.

      What about encrypted traffic? How can you tell it's "P2P traffic"? How about traffic from multiplayer games that uses a completely alien packet configuration that doesn't fit any "standard" mold because the company making the game had to design their own packet format on top of TCP/UDP? How do you discriminate between "good" and "bad" packets?

      You can't outlaw encryption. You'd get into a serious fight with banks that way (and, trust me, you DO NOT want a fight with a bank). You can't outlaw connecting on "nonstandard" ports, that would open another can of worms you do not want to touch.

      So please enlighten me how you'd like to enforce the "no encrypted P2P" rule.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    2. Re:A simple way to defeat this by nevali · · Score: 5, Informative

      What the hell do you think SSL is?

      No ISP would be plain retarded enough to block all encrypted traffic, on the grounds that it takes away a big reason for people to use the Internet (and thus their service) in the first place: buying stuff online.

      (Christ, I had to give up mod points to point this out)

  2. Bad news by Filip47 · · Score: 4, Informative

    This is bad news for us Belgians. We have but 3 major ISP's in the country and Scarlet is one of them. Soon, SABAM could attack the other two. Scarlet was the best choice to start, as it is the smallest of the three.