1.7.7 folks!

[1000possibleclaws]

What.cd banned 1.7.6. i don't know the details, but i think there's a backdoor issue with that version of the client.. Out of my trackers, TTi, as well as indietorrents don't yet work with this newest patch.. I guess the people who sticked with 1.6.1 kinda won on this one...

i hope 1.7.7 is an end all because all this shit has really gotten me ticked with utorrent

[filonome]

What.cd banned 1.7.6. i don't know the details, but i think there's a backdoor issue with that version of the client.. Out of my trackers, TTi, as well as indietorrents don't yet work with this newest patch.. I guess the people who sticked with 1.6.1 kinda one on this one...

i hope 1.7.7 is an end all because all this shit has really gotten me ticked with utorrent

lol, rtorrent ftw.

[0Ri0N]

OMG, not again!!!!!!!!!!!!!!!!

[Gish]

Java or no Java. thats not a hard one to figure out

[SCR]

when will this have an end .. i wonder.. 1.6.1 was everything i needed..

[FatBob]

i hope tracker admins who have banned utorrent 1.6.1 are reading this thread

[OnEyM]

omg, i'm tired of utorrent updates, if all the trackers hadn't ban 1.6.1 there would be less shit

btw, the only version of a torrent client under windows is 1.6.1, scn is my favorite tracker now

[peat moss]

i hope tracker admins who have banned utorrent 1.6.1 are reading this thread

What a joke , I'm tempted to just reinstall 1.6 and leave IPT or one like it as my tracker of choice . Fuck the rest of them , time to ditch the nay sayers and homo sites . :dabs:


Hey wait a minute I do have 25 invites to said tracker I never thought I could get rid of ...... JK LOL

[gbilly72]

utorrent has a history of releasing another version just a few days after a new version. I know it's free but programmers: get it right the first time!

[aysomc]

this is exactly why we made such a big deal about 1.6.1 being banned. this shit always happens with these new versions and they still havnt found anything wrong with 1.6.1.

[Zeus]

All this client banning and forced updating is getting annoying. If a client doesnt report dodgy stats then the tracker should allow it. Security problems are the users concern, not the trackers.

[fstrulz]

Why would you even upgrade from 1.6 to 1.7.x? If you don't trust the MPAA, which has been partnered with BitTorrent Inc. (since uTorrent 1.6.x), then you should just switch/stick with Azureus or rTorrent.

[pro267]

After ScT had banned versions prior to 1.7.6, it seems that TT had (unsurprisingly) decided to follow suit and forced an upgrade to 1.7.6. I imagine they will soon force an upgrade to 1.7.7 as well.

To the guy that was rooting for rtorrent: AFAIK, utorrent and rtorrent share the same code base, so don't be surprised if you're soon asked to upgrade as well.

[peat moss]

Why would you even upgrade from 1.6 to 1.7.x? If you don't trust the MPAA, which has been partnered with BitTorrent Inc. (since uTorrent 1.6.x), then you should just switch/stick with Azureus or rTorrent.



I think the whole point is some trackers banned anything under 1.7.5 . So most people being of kind community spirit or selfish concerns upgraded to the allowed one . Pretty easy to grasp really . :dabs:

[markupmaster]

I am a big fan of utorrent but this is starting to piss me off as well..


:(

[Hunim]

i've no problem with this... utorrent auto updates so.. no work for me!

[LubTheStaringCat]

I am getting the following term
Your client is spoofing message after upgrading to 1.7.7
Im not familiar with the term "spoofing", what does it mean?

[JohnDoe]

I don't mind upgrading utorrent, but this is really getting ridicules

[rvt]

Apparently there is a bug affecting all versions from 1.4 upwards.

The extension protocol crash bug affects 1.4, 1.5, 1.6, 1.7, and 1.8 builds releases to date.

The webui bug has a few details knocking about, but this one I can't find anything on it. At least with the webui you can work around it using a "real" webserver to forward messages to the webui on 127.0.0.1

[fOrUmAs]

yea its time again to upgrade lol

[nsk]

Sigh! :(

[lysine]

To the guy that was rooting for rtorrent: AFAIK, utorrent and rtorrent share the same code base, so don't be surprised if you're soon asked to upgrade as well.

and your supporting proof is where? I've never heard that, and seriously doubt it.

[Demigod]

uTorrent seems to be having a lot of trouble lately. Maybe it's better to just use Azureus temporarily and wait until these issues with uTorrent has been resolved.

[fOrUmAs]

uTorrent seems to be having a lot of trouble lately. Maybe it's better to just use Azureus temporarily and wait until these issues with uTorrent has been resolved.

yes that is true,they have it seems some problems with not so popular 1.7 versions but i dont agree that u should change client becuase of that,as u can see they at least fixing bugs in previous versions and trying to be more secure :)

[t0mmy]

oh man now i need to update again and utorrent page is playing up :(

[ByteKnight]

I don't see the problem, 1.7.6 is working perfectly for me. The older versions started crashing all the time so I switched back to 1.6
But recently I downloaded and installed the latest version and the crashing bug seems fixed.

[briand5379]

Is it just me or has uTorrent gone to shit. The 7th 1.7 release this is ridiculous and they wonder why people want to stay with 1.6.1.

[1000possibleclaws]

uTorrent seems to be having a lot of trouble lately. Maybe it's better to just use Azureus temporarily and wait until these issues with uTorrent has been resolved.

the problem with this is you'd have to port ALL your torrents to a new client.. thank god 1.7.7 is being allowed everywhere now, cause realistically i would never spend the time to switch over clients.. unless it was slowly and i finished seeding everything on utorrent, and dled new stuff from another client


Is it just me or has uTorrent gone to shit. The 7th 1.7 release this is ridiculous and they wonder why people want to stay with 1.6.1.

I actually havn't noticed much change aesthetically in the updates to be honest, except for vista support.. i thought all the changes were in coding for security

[rvt]

To the guy that was rooting for rtorrent: AFAIK, utorrent and rtorrent share the same code base, so don't be surprised if you're soon asked to upgrade as well.

and your supporting proof is where? I've never heard that, and seriously doubt it.

There wont be any supporting proof.

uTorrent = windows only, closed source
rtorrent = *nix, open source

They're both coded in c++ though, maybe that's it :P

[pro267]

and your supporting proof is where? I've never heard that, and seriously doubt it.

There wont be any supporting proof.

uTorrent = windows only, closed source
rtorrent = *nix, open source

They're both coded in c++ though, maybe that's it :P
I just ran some google searches to try and find where I got that impression from.
Oh, well, at least I used "AFAIK". You know, you can practically say whatever you want as long as you prefix it with AFAIK.. :P

Seriously though, I seem to have been misinformed. My mistake.

[bunny67]

someones taking the piss grr

[That1Guy]

damn Im glad I still have the 1.6.1 stand alone tucked in a folder :)

[_coder_]

I hope ScT unban 1.6.1.....but then again they have ego problems...

[ceasar]

I guess the people who sticked with 1.6.1 kinda won on this one...
Not really, hdbits banned everything lower than 1.7.6

[fOrUmAs]

I hope ScT unban 1.6.1.....but then again they have ego problems...


or someone trying to be smart :rolleyes:

The extension protocol crash bug affects 1.4, 1.5, 1.6, 1.7, and 1.8 builds releases to date. No update will be released for pre 1.7 builds. Upgrading is strongly recommended.

except 177

Fix: (potential) remote crash bug with extension protocol (affects all 1.4, 1.5, 1.6, 1.7, and 1.8 builds released to date)

[Submission]

1.6.1 is vulnerable why the hell are people keeping it around?

[briand5379]

My understanding is it doesn't effect 1.6.1 as sites that once had it banned have now started unbanning it.

This was posted one 1 site.
uTorrent 1.6.1 is immune and ok to use

[Roy.A]

I had 1.6.1 (build 490) and i updated it into 1.7.6 (when sites banned 1.6.1 etc.) . . .
then i saw sites are unbanning version 1.6.1 so i installed it again (i have the installation file) i had and have no problems with that version it seems to work just fine ...
now i see that 1.7.7 version . . . people are getting mad by the changes ~
i think im fine as long as sites wont ban 1.6.1 and as long it stays sane at my pc and wont do any stunts :D

[Optical]

1.6.1 seems to work alot smoother for some reason..

[grimms]

this is exactly why we made such a big deal about 1.6.1 being banned. this shit always happens with these new versions and they still havnt found anything wrong with 1.6.1.

Very true. Told you all utorrent 1.7.6 was buggy. I was getting crash dump errors twice a day. Never with 1.6.1 though. But i did upgrade to 1.7.7.

[Dark Archon]

who said 1.7.7 is out?

[buggyfresh]

here we go again!

[WarrenBuffet]

new update again?

[1000possibleclaws]

who said 1.7.7 is out?

I did, because I'm using it. go to utorrents website before accusing me of lying :P I had to manually download it, there's no auto-update yet, but trackers are banning 1.7.6. so I suggest either upgrading or downgrading, whichever you prefer.

[grimms]

who said 1.7.7 is out?

I did, because I'm using it. go to utorrents website before accusing me of lying :P I had to manually download it, there's no auto-update yet, but trackers are banning 1.7.6. so I suggest either upgrading or downgrading, whichever you prefer.

Yes bitmetv and others have already banned 1.7.6. uTorrent updates fast yeah?:lol:

[Tokeman]

Ok, time to update again. Not like its hard...

[grimms]

It's not but it could become tiresome to some and not to others. I guess it depends on my mood, if it becomes tiresome to me.

[lostdemon]

This is kind of annoying but I guess I fall in the not so tiresome category

[grimms]

Nothing wrong with that Lost Demon. Only reason why i would get tiresome is because before the ban on utorrent 1.6.1 i haven't had to update my client in like 2 1/2 years. Just takes some getting used to again i guess.

[smc]

this is ridiculous ..back to 1.6.1.

[grimms]

this is ridiculous ..back to 1.6.1.

Lol:lol:. Isn't it confusing. Every other day a new update.:lol: I actually like 1.7.7 so far though.

[SCR]

well i already have problems with 1.7.7: on TT it says : Failure : Your client is spoofing...and is banned in BCG

[grimms]

Damn your right. I just noticed it in the client BCG already banned this version. I'm goig back to ut 1.6.1. Damn i was seeding a game in 1.7.7 i hope i fdon't get int roble had to delete it cause bcg banned 1.7.7.

[fOrUmAs]

177 is allowed on most tracker that i use so np here,also give some time to BC or TT becuase they need to test it first lol..:)

[stoi]

yeah its not banned on BCG, it just is not allowed yet.

but i agree this is getting silly, this is twice they they have brought out an update and then a day or 2 later another one.

im sticking to 1.6.1 at least i know thats fine for me.

[davidw89]

allow 1.6.1 and 1.7.6 for heavens sake..and leave it like that for some time..

[Cabalo]

uTorrent seems to be having a lot of trouble lately. Maybe it's better to just use Azureus temporarily and wait until these issues with uTorrent has been resolved.
... if only azureus wasn't so resources hungry... i'd switch immediately. as for now i'll stick with utorrent, though it lost all its charm since banning of 1.6.1

[Tokeman]

well I havn't updated yet, since its not in the auto update yet, and I've had no trouble seeding still with 1.7.6 on any of my trackers. It may be ban'd but they are not enforcing it yet...
Just food for thought for those of you not wanting to upgrade/downgrade/switch yet.

[bikernin]

damn..the rate at which threads are opening up about utorrent we will soon need a separate section for it here on FST
post your cribbings about utorrent here :lol:
i still dunno why they have to hit the panic button everytime a new version is released. 1.6.1 was so safe and nice. still found nothing wrong with it

[Tokeman]

damn..the rate at which threads are opening up about utorrent we will soon need a separate section for it here on FST
post your cribbings about utorrent here :lol:
i still dunno why they have to hit the panic button everytime a new version is released. 1.6.1 was so safe and nice. still found nothing wrong with it

from the utorrent forums, not sure about the validity, but i'm sure a dev will post about this sooner or later on this post:

"The original bug that was fixed in 1.7.6 was not present in 1.6.1.
The bug that 1.7.7 fixes IS present in 1.6.1 and will NOT be fixed in a new 1.6.x build."

found here: http://forum.utorrent.com/viewtopic.php?id=29330&p=12

I'd wait for a post from some one in the utorrent team, but this sounds like reason enough to upgrade to me. better safe then sorry I say.
I'm upgrading now.

EDIT:
Confirmation from a mod, same thread:

"There was some miscommunication when 1.7.6 was announced that caused the changelog for 1.7.6 to initially include 1.6.x as an affected branch (when in fact it isn't affected by that bug). The latest version (1.7.7) actually does fix a potential security flaw that has existed in µTorrent's implementation of the extension protocol since 1.4.

Which change?
- Fix: (potential) remote crash bug with extension protocol (affects all 1.4, 1.5, 1.6, 1.7, and 1.8 builds released to date)"



Time to upgrade you 1.6.1 people, or find a new client.

[VIZFX]

If its not broke, don't fix it!

[Tokeman]

If its not broke, don't fix it!
It is broke, read my post page 6 for proof.

[chachinator]

when will it be on the update server?

[Tokeman]

double post, delete me plz :|

[SenorBubbz]

damn..the rate at which threads are opening up about utorrent we will soon need a separate section for it here on FST
post your cribbings about utorrent here :lol:
i still dunno why they have to hit the panic button everytime a new version is released. 1.6.1 was so safe and nice. still found nothing wrong with it

from the utorrent forums, not sure about the validity, but i'm sure a dev will post about this sooner or later on this post:

"The original bug that was fixed in 1.7.6 was not present in 1.6.1.
The bug that 1.7.7 fixes IS present in 1.6.1 and will NOT be fixed in a new 1.6.x build."

found here: http://forum.utorrent.com/viewtopic.php?id=29330&p=12

I'd wait for a post from some one in the utorrent team, but this sounds like reason enough to upgrade to me. better safe then sorry I say.
I'm upgrading now.

EDIT:
Confirmation from a mod, same thread:

"There was some miscommunication when 1.7.6 was announced that caused the changelog for 1.7.6 to initially include 1.6.x as an affected branch (when in fact it isn't affected by that bug). The latest version (1.7.7) actually does fix a potential security flaw that has existed in µTorrent's implementation of the extension protocol since 1.4.


Which change?
- Fix: (potential) remote crash bug with extension protocol (affects all 1.4, 1.5, 1.6, 1.7, and 1.8 builds released to date)"





Time to upgrade you 1.6.1 people, or find a new client.



Down with 1.6.1!!

[rvt]

If its not broke, don't fix it!
It is broke, read my post page 6 for proof.
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.

[sear]

from the utorrent forums, not sure about the validity, but i'm sure a dev will post about this sooner or later on this post:

"The original bug that was fixed in 1.7.6 was not present in 1.6.1.
The bug that 1.7.7 fixes IS present in 1.6.1 and will NOT be fixed in a new 1.6.x build."

found here: http://forum.utorrent.com/viewtopic.php?id=29330&p=12

I'd wait for a post from some one in the utorrent team, but this sounds like reason enough to upgrade to me. better safe then sorry I say.
I'm upgrading now.

EDIT:
Confirmation from a mod, same thread:

"There was some miscommunication when 1.7.6 was announced that caused the changelog for 1.7.6 to initially include 1.6.x as an affected branch (when in fact it isn't affected by that bug). The latest version (1.7.7) actually does fix a potential security flaw that has existed in µTorrent's implementation of the extension protocol since 1.4.


Which change?
- Fix: (potential) remote crash bug with extension protocol (affects all 1.4, 1.5, 1.6, 1.7, and 1.8 builds released to date)"





Time to upgrade you 1.6.1 people, or find a new client.



Down with 1.6.1!!



Meh...I don't even know if I believe this shit. Last time they said 1.6.1 was affected then it wasn't then it was :P and now this.

After all this shit I'm thinking it's time to fuck UTorrent off all together. BitTorrent inc has completely ruined the best client out there.

[suppli3r]

update again :wacko:

[peat moss]

update again :wacko:

This one may have actually helped my lil problem with speed issues . :)

[REDATTACK]

Azureus is the best torrent program that i have ever seen

No problems at all with trackers not like utorrent or other torrent programs

[Something Else]

I don't care which utorrent I use. I just wish the sites would agree instead of all banning different versions. It's pathetic.

[TankGrrl]

1.6.1 is vulnerable why the hell are people keeping it around?

because it is not owned by the MPAA p2p police!





Meh...I don't even know if I believe this shit. Last time they said 1.6.1 was affected then it wasn't then it was :P and now this.

After all this shit I'm thinking it's time to fuck UTorrent off all together. BitTorrent inc has completely ruined the best client out there.

i used to love utorrent but all this is making me want to find a new proggy to use...

[Tokeman]

uTorrent is still the king of torrent programs. Who cares who owns it as long as it does not transmit any information to them? If it is still doing what its designed to, whats the big deal? As for the updates, if there is exploits, I'm glad they are addressing them with updates. I do not wish to be exploited, perhaps you all do?
Windows releases updates once a week for christs sakes, this is how the tech world goes, you should all be used to it by now. Mainstream programs have to have the capibility to fix bugs as they are found, as they are attacked simply because they are popular.

[sscape]

Time for an upgrade.

[YoYoY]

Edit : I DO NOT UNDERSTAND ANYTHING I'M OUT OF THIS DAMN THREAD :P

[wooh]

1.7.7 is here:p

[typeoholic]

They made the uTorrent icon just a bit darker shade of green than it already was. :P

[The Wanderer]

There is a new icon for 1.8. ;)

[ghurka]

Oh for a decent BT client other than uTorrent or Azureus. Just a pity there is not an alternative acceptable by all trackers. Anyone got any ideas?

[wildbytes]

It is broke, read my post page 6 for proof.
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

[fOrUmAs]

There is a new icon for 1.8. ;)

i hope is good:),i dont use 1.8(alpha) untill they released stable version.

[Tokeman]

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]

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 :P

[Tokeman]

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 :P

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]

Thats true...:cool:

[SHINKEN]

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]

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]

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 (http://aluigi.altervista.org/), with references, but ignoring the µTorrent forums:

Extension protocol (http://www.rasterbar.com/products/libtorrent/extension_protocol.html) 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 (http://aluigi.altervista.org/adv/ruttorrent-adv.txt) 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 (http://download.utorrent.com/1.7.7/utorrent-1.7.7.txt) mistakenly listed 1.6.x as affected by the bug, but Auriemma reports that it is not, and nxnod.net has posted a video (http://nxnod.net/utorrent/) proving that it is not.***
Fixed in 1.7.7

WebUI (http://www.utorrent.com/webui-guide.php) 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 (http://aluigi.altervista.org/adv/ruttorrent2-adv.txtt) 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 (http://www.utorrent.com/webui-guide.php)).
Fixed in 1.7.7

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

[znik]

Czone urges us NOT to use utorrent 1.7.7 !
"Your account might be disabled for fake reasons." :unsure:

Other trackers like TTi do not allow anything older than 1.7.7... :frusty:

How unsafe is it really to use the lattest utorrent version? :ermm:
Back to azureus? :wacko:

[marquinhooo]

Thanks for info!!

Its time to upgrade!! =)

[polymemnon]

On the issue of stability or vulnerability to attack, 1.7.7 is as safe as any internet software that has had all known bugs fixed. For admins that ban 1.7.7, this isn't (or shouldn't be) an issue.

On the issue of privacy and security - security meaning safety from RIAA/MPAA - some admins believe that 1.7.x versions are compromised, since BitTorrent bought µTorrent at the end of 2006, and BitTorrent has taken a well-known stand against unauthorized file-sharing. As far as I know, no proof of "phoning home" or suchlike has been posted (some early reports of this were traced to DHT), but some admins, who face harassment and lawsuits in the U.S., or arrest elsewhere, are understandably taking the "better safe than sorry" strategy, and banning all versions past 1.6.1, or even earlier.

Based on the facts, the only banning policy that makes no sense whatsoever is allowing 1.7.6, which is vulnerable to WebUI and protocol extension attacks, and banning 1.7.7, which is safe from them.

As far as CZone goes, "Your account might be disabled for fake reasons," is awfully cryptic. I don't know what "fake reasons" means, or if this indicates that they may allow 1.7.7 later. I know of other trackers that ban all of 1.7.x, including 1.7.7, but none that ban 1.7.7 but allow other 1.7.x versions.