Unfortunately, the loophole is that the RIAA can keep generating IP's out the wazoo, creating a whack-a-mole [tuxedo.org] type of situation.
They probably will, as will the subcontracters who carry out the work. But odds are they'll all be working within fixed ranges of IPs. As long as someone out there is proactively looking for them and occasionally posts lists of IP addresses and DNS entries for the RIAA hack squad they can be blocked by the ISPs, network managers, and by savvy home network users. Kinda like those host files that block a few thousand DNS entries that host pop-ups and adware.
BTW - how would one go about getting info on which IPs are being used by Overpeer, Vidius, NetPD, Media Defender and MediaForce? I'd love to add theirs to a bogus routing table sometime in the not so distant future....
Slashdot Mirror
Unfortunately, the loophole is that the RIAA can keep generating IP's out the wazoo, creating a whack-a-mole [tuxedo.org] type of situation. They probably will, as will the subcontracters who carry out the work. But odds are they'll all be working within fixed ranges of IPs. As long as someone out there is proactively looking for them and occasionally posts lists of IP addresses and DNS entries for the RIAA hack squad they can be blocked by the ISPs, network managers, and by savvy home network users. Kinda like those host files that block a few thousand DNS entries that host pop-ups and adware. BTW - how would one go about getting info on which IPs are being used by Overpeer, Vidius, NetPD, Media Defender and MediaForce? I'd love to add theirs to a bogus routing table sometime in the not so distant future....