Slashdot Mirror
BitTorrent Devs Introduce Comcast-Proof Encryption
Dean Garfield writes "An article at TorrentFreak notes that several BitTorrent developers have proposed a new protocol extension with the ability to bypass the BitTorrent interfering techniques used by Comcast and other ISPs. 'This new form of encryption will be implemented in BitTorrent clients including uTorrent, so Comcast subscribers are free to share again. The goal of this new type of encryption (or obfuscation) is to prevent ISPs from blocking or disrupting BitTorrent traffic connections that span between the receiver of a tracker response and any peer IP-port appearing in that tracker response, according to the proposal.'"
Unless one side suddenly blows away the other, I don't see this ending. It may breed innovation, but said innovation only seems useful for this one problem.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
Most blocking systems use traffic analysis to block encrypted protocols, even the ones pretending to be something else. There's no way you can confuse p2p sharing with normal browsing if you look at the pattern of data flows.
Too bad we even have to fight this forgery by Comcast, but a technical option has its advantages, since a legislative option might get watered down by lobbyists and congress.
Encryption is always a good thing. The more people that use encryption, the less eavesdropping there will be.
How about, "if you have nothing to hide, hide it anyways"?
If I have nothing to hide, don't search me
Comcast will now probably simply impose soft traffic caps and soft caps on the number of connections users can make.
Well currently the state of the art is in favor of encryption, rather than cryptanalysis, so I don't think that the advantage is automatically Comcast's. They could probably do some fairly sophisticated traffic analysis, but at the end of the day, they're not actually going to break the encryption and get at the contents, and they can't block all encrypted traffic because it's too critical for other purposes.
They can force the BitTorrent devs to produce a new version every few months, but in the long run I think they're on the losing end of the war -- if they want to stay in the data-transportation business, and assuming there aren't any major breakthroughs in cryptanalysis that render modern public-key technologies useless.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
Comcast is trying to spin their actions as promoting fair use of the their networks. The truth is that ISP's profit from having data dumped INTO their network and have to pay hard cash for data LEAVING their network. By injecting RST's into the peers seeding traffic, they promote an asymmetric data flow that brings more data (and therefore money) into their network, while minimizing the money they have to pay other ISP's for data going out. This proposal provides protection against the throttling of their upstream Bittorrent traffic only if the ISP is not aware of the info_hash of the torrent. Once this data is known it is possible to apply common data tagging and congestion control techniques to squelch this traffic. All the service provider (or application developers like SandVine) has to do is monitor the common torrent sites, and dynamically update this hashes into the network filters. This is sure to deny a majority of the torrent traffic out there (movies, linux distro's, etc). Colin McNamara CCIE #18233
Colin McNamara - CCIE #18233 "The difficult we do immediately, the impossible just takes a little longer"
I am just a measly CCNA.
I am not worthy.
m(_ _)m
there is also a UDP Tracker Protocol for BitTorrent, UDP doesn't even hear the RST packet. Comcast will have to figure out a way to turn off something that doesn't have an off switch.
Apocalypse Cancelled, Sorry, No Ticket Refunds
Now Comacast will need to keep a list of connections in order to guess that a torrent is running, instead of just looking at the packet. Good luck on that without a massive infrastructure upgrade.
"To those who are overly cautious, everything is impossible. "
How long is it until they start throttling encrypted traffic too?
Wonder what the public key field is for?
Nope. It's the TCP connection between two peers that Comcast is attacking, not the connection between the peer and the tracker. Using UDP for the latter doesn't solve anything.
Visual IRC: Fast. Powerful. Free.
They don't care about any protocol analysis. Any sufficiently long-lived, high volume, traffic flow between two IP addresses gets hit. I've had IPSEC VPN connections behave strangely and opened tickets, where the techs have admitted I had "accidentally" been flagged (IE, the IPSEC endpoints weren't on the whitelist, even though I have business class service).
The only way around this is to open multiple connections to different addresses, transfer small amounts per connection, and then shut it down, opening the next connection to a different endpoint. It requires a total reengineering of P2P, although the BitTorrent mechanism is closest to what would work.
If they aren't already doing it (I dont know the exact technical details of what they are doing), ISPs like Comcast will simply start looking for anyone uploading large amounts of data (especially if they are uploading to a bunch of different people at once) and block that.
I'm surprised it took this long for the Bittorrent Devs to respond. Encryption is not a complete solution, as I have stated before, but it is a beginning. That is for certain .
.
It's going to get a lot more interesting from here on out. In the end, it will only benefit the consumers since they will receive technology that allows them to communicate a little more privately, and perhaps with a little luck, more anonymously too. One could only hope that TOR/Freenet technologies become as ubiquitous in their use as email. Perhaps a hybrid system with elements of Freenet, TOR, and Bittorrent all wrapped up into one would do the trick. I certainly think so.
I think, actually I know, that Comcast has fired the first shot in a losing battle.
I also just can't help pointing out the similarities to the Drug War. A million or so people in prison, and yet there are still plenty of users and suppliers. I would almost say it has effectively made no difference in the amount of people using drugs, or selling them. Especially, since the amount of drugs being sold and used in prisons is even higher then on the street.
So what is the point? If history has taught us anything, it is that governments (corporations even more so) will consistently fail at their attempts to limit/eliminate popular behavior. The elements may change from time to time, but the end result is always the same. The people will find a way to continue their behavior
"Greetings, Professor Falken. Strange game. The only winning move is not to play."
One of the things I'm curious about is what kind of collateral damage this kind of thing does to legitimate traffic. Oddly enough, I couldn't get to expedia.com, transformers.com (hey, I have an eight-year-old), and store.apple.com when I first got Comcast. A couple of months later, when the news first broke that they were screwing with the traffic, those sites suddenly started working. Nothing changed at my house, and all of them started working at once.
Possibly coincidence. Possibly not.
Anything stronger than rot-13 will do.
Even if it only takes an ISP 0.1 seconds to "crack" a packet then there's no way he can crack the millions of packets per second flowing through his routers.
No sig today...
If they ever do manage to completely block P2P then they might find themselves looking at a bunch of customers who only want 300kbit connections instead of 20mbits. What are they going to do? Slash their prices to the same as the small ISPs who can offer cheaper/slower connections? I think not.
No sig today...
Reportedly most of it comes from botnets:
Insecure machines that were taken over by hackers and whose clueless owners did not notice anything. Or even don't care.
Now if ISPs start selling traffic by the gigabyte (again - it was not uncommon a few years ago), the owner of those spam-slaves would notice it on their internet bills. At that point, I think securing one's machine would become a lot more popular and the botnets would shrink. Overall result:
less spam and DDOS attacks.
Considering the inbound hacking attempts, my father still has a 2 GByte/month plan and so far I've heard no complaints about suddenly increasing bills. So it seems to be not that much.
C - the footgun of programming languages
Wouldn't breaking the encryption be a violation of the dmca?? I think that would be sweet.
I have mod points and I am not afraid to use them.