New BitTorrent Encryption on the way!

All you Comcast and Cox customers that are getting screwed by not being able to seed after completion can rejoice!


BitTorrent Developers Introduce Comcast Busting Encryption

http://torrentfreak.com/bittorrent-d...yption-080215/


The sweet thing is that this new crypt is being developed by BitTorrent itself so you know this isn't some untested beta type work around...Thx Bram!:)
And uTorrent is in on it as well!! :w00t:

Soon Comcast will have a few million dollars worth of useless Sandvine boxes...money that should have been spent upgrading their network!

Are we talking about the same guys that made the original crappy BitTorrent and repeatedly fucked up a perfectly good client (utorrent)?
It sure sounds promising..

Quote:

---

Originally Posted by pro267

Are we talking about the same guys that made the original crappy BitTorrent and repeatedly fucked up a perfectly good client (utorrent)?
It sure sounds promising..

---

No...I believe we're talking about the people who created the BitTorrent protocol along with coders/devs from uTorrent and elsewhere I'm sure.

aren't https trackers enough for that? :S

Quote:

---

Originally Posted by yayyyyyy

aren't https trackers enough for that? :S

---

Don't think so and not many SSL enabled trackers either (besides ScT)

More info here:

http://torrentfreak.com/comcast-thro...ng-impossible/


And here: (note the recommended encryption level for Comcast)

http://azureuswiki.com/index.php/Bad...tes_of_America

This is great!

:)

Thanks for letting us know!

:)

Quote:

---

Originally Posted by Zaxx

The sweet thing is that this new crypt is being developed by BitTorrent itself so you know this isn't some untested beta type work around...Thx Bram!:)

---

Read my comments on TF, 26 and 30. It offers no real protection against torrents being cut off or slowed by your ISP, and requires more work all round to implement than SSL. Also, you wont find this on uT 1.6.1 etc, whereas you will find SSL support :P

Quote:

---

Don't think so and not many SSL enabled trackers either (besides ScT)

---

Yep, SSL beats this one hands down for beating throttling. It is also more likely to be implemented tracker side.

The thing with this new one is that it requires the tracker devs to implement an RC4 method in their code. SSL requires nothing more than a quick config change in the webserver.

If there are as few trackers running SSL as you say, there will be even less running this new method as it will take more work to implement.

Thanks for the insight. Lucky for me, my node (formerly owned by adelphia) isn't getting hit by the forged RSTs. If I was getting hammered, I'd already be going the vpn route like most.

Now all we need is a cheaper way to get signed certificates, without all the address verification crap verisign likes to do.

A self signed SSL cert leaves you open to a man in the middle attack by your ISP, unless your client supports storage of trusted self signed certs.

The idea is good but how long will it work before isps think of someting else to come back with i don't know how long previous methods have worked or the history behind it lets just hope it will last a long time as stated it's an up and down ride. there was an article somewhere about an average member of the public is suing comcast i wonder how that is turning out.