+ - Beating Comcast (now without iptables!)->
Submitted
by
The author
The author writes "A number of solutions exist to Comcast's spurious reset message attack on bittorrent. However, these solutions demand iptable wizardry and super-user permissions. I have a simple way of circumventing TCP reset flag censorship: a TCP-over-UDP tunnel with user-level TCP stacks. Importantly, it only needs end-users to upgrade their torrent client. Unfortunately, it can't be finished now because I'm swamped finishing my Thesis instead. I've prepared a short document outlining the solution, and I have the hardest part already implemented as a library. All that's left is a Bittorrent developer (or perhaps Comcast subscriber) to read this and decide whether its worth lending a hand.
For the record, I don't use Comcast, but I object to violating the venerable TCP Protocol:
"As a general rule, reset (RST) must be sent whenever a segment arrives which apparently is not intended for the current connection. A reset must not be sent if it is not clear that this is the case." Using resets to censor connections deemed unfit by an ISP is not a specified use."
Link to Original Source
For the record, I don't use Comcast, but I object to violating the venerable TCP Protocol:
"As a general rule, reset (RST) must be sent whenever a segment arrives which apparently is not intended for the current connection. A reset must not be sent if it is not clear that this is the case." Using resets to censor connections deemed unfit by an ISP is not a specified use."
Link to Original Source
Beating Comcast (now without iptables!) More Login
Beating Comcast (now without iptables!)