To BT site staff about utorrent 1.6.1 !

[FatBob]

done rvt !

really appreciate all your hard work

thread updated

[bigdaddykane]

for those looking for a link to the uttorent 1.6 i have uploaded it to rapidshare i had it in a registry cd that i had put away so here is the link you all.

http://rapidshare.com/files/85656043...stall.rar.html

[waterloo]

^ http://filehippo.com/download_utorrent :/

[rvt]

Had to dash out this morning, but here's the link for the new changelog.
http://72.20.34.146/1.7.6/utorrent-1.7.6.txt

You can verify that the IP is utorrents by typing this in a console window:

nslookup download.utorrent.com

One of the two addresses sent back will be the IP above.

[FatBob]

utorrent 1.6.1 will no longer be banned. It is official.

revtt

[pandabear]

I have to ask. How can people say 1.6.1 is so great, when in that change log there is heaps of changes in subsequent 1.7.xx versions, meaning those bugs were present in 1.6.1. Unless i am wrong to assume 1.7 was just a carry on from 1.6, with some BT inc coding.

[rvt]

A lot of the fixes in 1.7.0 1065 were for minor issues, such as logging and display issues.

If we eliminate all logging and UI fixes, we're left with:

1) - Fix: Stopped/paused torrents no longer hold up auto shutdown
2) - Fix: Various minor issues with HTTP client implementation (error handling, parsing)
3) - Fix: Incoming HTTP connections could sometimes go dead (event dispatch problem)
4) - Fix: Some internal size calculations weren't 64-bit clean
5) - Fix: Correct WinSock version detection - it should fail now if it detects the wrong version
6) - Fix: Correct acquisition of special operating system paths (such as the windows directory) on Windows 95 family
7) - Fix: Fix shortcut creation for Windows 95 family
8) - Fix: Fix diskspace information on Windows 95 family
9) - Fix: Shutdown on finish option will now shutdown the machine, even if it is locked
10) - Fix: Fix file association if uTorrent is installed after BitTorrent mainline client
11) - Fix: 307 redirection HTTP code is now handled, instead of an error (i.e. jamendo.com)
12) - Fix: Association check for limited users

1) auto shutdown may be held up, it's not a show stopper.
2) possibly affects announce/scrape, but could be just related to searches. Either way, it's listed as minor.
3) Incoming HTTP connections should only happen on the web ui. Presumably a refresh would work.
4) Would cause the calculated size to be wrong. Not sure where this would have an effect.
5) If winsock version is important, it should fail when you try to do something anyway. This can just warn you ahead of time.
6) Who still uses 95?
7) see 6
8) see 6
9) Not sure what would cause a machine to be "locked" but is it a good idea to shut down if it is?
10) Easy enough to fix as a user anyway.
11) Quick testing shows a 307 redirect is not in place on either their scrape or announce URLs. There may be certain torrents affected by this, but there is not really any place for 307 in a tracker. 307 tells the client to switch to POST instead of GET, yet the BT spec shows all passed variables in GET format. Possible affects RSS or searches from there though.
12) Again, it's easy to fix associations as a user. This is more of a UI bug.

Everything fixed in subsequent versions cannot be automatically attributed to 1.6.1. In build 1088, the fix for bandwidth allocation selection may be to repair something broken in build 1065.

[fOrUmAs]

I have to ask. How can people say 1.6.1 is so great, when in that change log there is heaps of changes in subsequent 1.7.xx versions, meaning those bugs were present in 1.6.1. Unless i am wrong to assume 1.7 was just a carry on from 1.6, with some BT inc coding.

because of paranoia,they think that after 161 all version of utorrent have some *spy program* in new utorrent that send your ip to MPAA or RIAA lol..

but after so many testing from many and i mean many privates trackers there wasnt found any proof of that..

so that is why some members bitching all the time to be allowed 161 on some trackers,but they should know no matter what cliend they(we all use) u are not safe..

[rvt]

It's not just paranoia about spyware. Witness how every single build in the 1.7.x branch is remotely crashable. Because the crash is caused by an overflow, it may even be exploitable to run code.
This was discovered after 10 months, despite all the testing. How long till other stuff is discovered?

1.7.6 has also not been tested as much as claimed. 1.7.6 was released 8 days ago, so it has at most 8 days of testing behind it.
1.6.1 was released nearly a year ago, so it has a years worth of testing behind it.
Anyway, there are not a lot of sites that actually conduct their own testing. Every single one of the sites that had to post a correction about 1.6.1 followed someone elses testing. There are a few people on a few sites who actually conduct any of their own testing. Would you trust any of the sites who could not even confirm that 1.6.x was not affected to tell you what is safe and what isn't? If you do, I know a nigerian banker who can get you some free money.

There are also a whole range of problems that affect various people when they try to run any 1.7.x version. Problems that do not exist in 1.6.1. It is simply not possible for everyone to run the latest version.

[FatBob]

any news about downgrading 1.7.6 to 1.6.1 on SCT ?