1.7.7 folks!

**fOrUmAs** · 01-30-2008, 03:08 PM

Originally Posted by The Wanderer

There is a new icon for 1.8.

i hope is good

,i dont use 1.8(alpha) untill they released stable version.

**Tokeman** · 01-30-2008, 03:12 PM

Originally Posted by wildbytes

Originally Posted by rvt

That's not any kind of proof. It is a claim made by uT staffers which cannot be backed up by anybody.

Take one group of uT staffers willing to lie about things so 1.6.1 will be killed off, a complete lack of information on how to recreate the bug, and the lack of even a single report in their bug forum about it and they'll have to do more to convince me.

They already got it wrong last time, this time there is not even the slightest chance for anyone else to verify their claims. It's extremely convenient for them.

I wont be recommending any upgrades till I can verify this myself.

The reason for them wanting everyone out of UT1.6.1 is simple, they were not the makers of the 1.6.1. Bittorrent inc bought ut after the ut 1.6.1 release. Stick with UT 1.6.1 as there is nothing wrong with it.

Maybe every site should just ban Utorrent and just be done with it. Utorrent is only hurtting them self with all the lies and BS.

Wild

and just how long do you expect people to continue using this outdated version? I mean, there is not 1 program out there that isn't updated regularly that is worth a damn, and no one uses old outdated programs unless theres problems with the new versions. WHy is it different here? Just because of PR error? That doesn't sound like a logical reason to use outdated versions to me.

**rvt** · 01-30-2008, 04:18 PM

If you check out the number of problems people are having with 1.7.x when upgrading from 1.6.x on the uT forums, 1.7 starts to look like windows vista. A buggy POS with feature bloat.

There are definite reasons for using an older, more stable version of a program rather than the latest unstable version.

BTW, we're all still waiting on proof of the existance of this latest bug from firon. He offered to show proof but has since changed his mind. He's been in IRC claiming that an extended messaging bug is exploitable by both direct connections and malformed torrents. This presents a problem in that unless the extended messaging is passing the torrent file, or the extended messaging is being used to rebuild the torrent file, this is not a single bug.

This whole episode smells. The reason they give for wanting everyone off 1.6.1 is because they do not offer support for it. Easy enough to state that you will not offer support, but it's not a reason to resort to lies, FUD and the slandering of your own product. Unless they start backing up their claims with proof, they just look more and more like they have some big, secret, reason to push 1.7.x and that can only fuel conspiracy theories.

Edit: he also claims that bittorrent official, libtorrent, transmission and bitcomet are affected, everything but azureus. So the word from uT is that if you want safety, you should use Az

**Tokeman** · 01-30-2008, 04:57 PM

Originally Posted by rvt

If you check out the number of problems people are having with 1.7.x when upgrading from 1.6.x on the uT forums, 1.7 starts to look like windows vista. A buggy POS with feature bloat.

There are definite reasons for using an older, more stable version of a program rather than the latest unstable version.

BTW, we're all still waiting on proof of the existance of this latest bug from firon. He offered to show proof but has since changed his mind. He's been in IRC claiming that an extended messaging bug is exploitable by both direct connections and malformed torrents. This presents a problem in that unless the extended messaging is passing the torrent file, or the extended messaging is being used to rebuild the torrent file, this is not a single bug.

This whole episode smells. The reason they give for wanting everyone off 1.6.1 is because they do not offer support for it. Easy enough to state that you will not offer support, but it's not a reason to resort to lies, FUD and the slandering of your own product. Unless they start backing up their claims with proof, they just look more and more like they have some big, secret, reason to push 1.7.x and that can only fuel conspiracy theories.

Edit: he also claims that bittorrent official, libtorrent, transmission and bitcomet are affected, everything but azureus. So the word from uT is that if you want safety, you should use Az

Although I agree with most of what you've stated (you make some great points), think of it this way. Many programs over the ages have issues with updates when you are way out of date. 1.6.x is old and outdated, and there is bound to be issues trying to skip a ton of version updates to the latest one. Best thing would be to save your settings, totally remove, and install the lates. Doing this I would bet dollars to dounuts that they would not have some of the issues they are experiencing, but I bet less then 5% of people on 1.6.x took this into consideration when trying to apply the latest version. Since 1.6.x isn't supported, trying to 'upgrade' from it would be like trying to upgrade from win98 to vista, not going to work.

**Georgo Smart** · 01-30-2008, 05:44 PM

Thats true...

**SHINKEN** · 01-30-2008, 06:12 PM

That's why it's always good to keep a backup copy of something before upgrading. If there are bugs with new one, just switch back.

Good topic though, as it helps admins look into these issues more.

**undercover1** · 02-09-2008, 11:23 PM

czone suggesting not to use the 1.7.7:
"DO not use utorrent 1.7.7 Your account might be disabled for fake reasons. Use only utorrent 1.7.6 or utorrent 1.6.1."

So they are banning the 1.7.7? Im kinda tired on that i have to use different versions of the utorrent nearly on every site, but this is the best client, i dont want to change.

**polymemnon** · 02-10-2008, 11:34 PM

Some of us distrust what the µTorrent admins say, since they're employed by BitTorrent, so here's a summary of the two remote crash bugs discovered by Luigi Auriemma, with references, but ignoring the µTorrent forums:

Extension protocol crash bug -
Bug info: Clients can be crashed by receiving long client version unicode strings to the static buffer visible on the "Peers" tab of the client . Luigi Auriemma's advisory was published on Jan. 16 '08.

Clients affected:
1.4.x through 1.7.6 build 7859, and 1.8 through 7834
Except 1.6.x
**At one point, The µTorrent changelog mistakenly listed 1.6.x as affected by the bug, but Auriemma reports that it is not, and nxnod.net has posted a video proving that it is not.***
Fixed in 1.7.7

WebUI crash bug -
Bug info: Clients can be crashed by receiving a series of HTTP requests with increasingly long Range headers, exhausting available memory. Luigi Auriemma's advisory was published on Jan. 27 '08.

Clients affected:
the µTorrent changelog doesn't specify, but WebUI was included as a closed beta in versions as far back as 1.5, and the first public release worked with 1.6.1
(see the µTorrent WebUI Guide).
Fixed in 1.7.7

So the question is, can you crash the 1.6.1 client by exploiting the WebUI bug?