Clean uTorrent 3.5.5 Build 45838

[anon]

SB-Innovation Presents

>>>>>> Clean uTorrent 3.5.5 Build 45838 <<<<<<





╔═══════════════════════════╗
Coded by:
╚═══════════════════════════╝

>>>>>> BitTorrent Inc. <<<<<<

╔═══════════════════════════╗
Modded by:
╚═══════════════════════════╝

>>>>>> anon <<<<<<

╔═══════════════════════════╗
Changelog / Features:
╚═══════════════════════════╝

· Removed all advertisements and social networking features
· Removed all the call-homes I could find
· Trimmed the executable by almost 2 MB by stripping binary blobs, HTML and digital signature
· Added DHT Patch v2: allows the use of DHT, PEX and LPD for private torrents, but does not enable them by default
· Added /LARGEADDRESSAWARE patch: allows the process to use up to 4 GB of RAM on 64-bit systems, or up to 3 GB on 32-bit systems configured to support it (the disk cache is still limited to 1800 MB)
· Added rss.update_interval patch: allows values lower than 5
· There are no cheating features, it's just for those who want a lightweight client

╔═══════════════════════════╗
Known issues:
╚═══════════════════════════╝

· "Upgrade to Pro" always appears in the sidebar.
Workaround: go to Options -> Preferences -> Advanced. Close the window, then do the same again but hold Shift+F2 before clicking on Preferences. Find gui.show_plus_upsell_nodes and set it to false. That setting is ignored on startup, so you'll have to do this every time you run the program.

· A very rare (once per six months of 24/7 runtime in average) issue that causes the program to crash silently. Not known if it's due to the mod or just a bug in uTorrent itself.

· Clicking where the globe icon would be in the bottom right corner of the window still opens the Preferences dialog.

· Ticking "Enable protocol enhancements" in the settings is not recommended, as said enhancements may rely on removed features.

· uTorrent will default to TLS 1.0 if no Schannel policies are set, which means many HTTPS trackers won't work. Merging the bundled registry file will solve this.

╔═══════════════════════════╗
Technical information:
╚═══════════════════════════╝

· Find the official uTorrent release matching the build number the mod is based on; extract Carrier.exe from it using 7-Zip or similar
· Use unsigntool to remove the digital certificate from Carrier.exe
· Use UPX to decompress said executable
· Use Resource Hacker to remove all resources of type CSS, GIF, JS, PNG, RCData and HTML from it
· At this point, filesize should be identical to the mod's and you'll be able to spot all the changes I've made with any binary comparison tool.
· The PE timestamp has been deliberately set to 0x00000000, and the checksum can be corrected using PEChkSum

· settings.dat: comes preconfigured to disable all advertisements, call-homes and non-essential features
· updates.dat: dummy read-only file that prevents uTorrent from storing data about (manual) client updates
· social.bmp: effectively hides the Facebook, Twitter and language icons in the status bar by replacing them with 100% transparent ones
· TLS Fix.reg: sets several Schannel registry entries to specifically allow TLS 1.x secure protocols
· utorrent.lng: official language pack file
· utorrent-355-45838.chm: official help file

[sashiagustina]

The latest one rearranged interface elements after more than a decade, and I don't want to "relearn" the program. The old version works fine in any case.

no bugs in that version ?

[anon]

None that I have noticed. By the way, you said on another thread that you use Windows 10, so why not help me with this?

I need some help from anyone running Windows 10 v1903 or above. Go to your Internet Settings, disable SSL 3.0 and enable all versions of TLS up to 1.3, then send me the output of the following commands.

reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings" /v "SecureProtocols"
reg query "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols" /s

[sashiagustina]

None that I have noticed. By the way, you said on another thread that you use Windows 10, so why not help me with this?

and how is the effect of this command ? i have to be sure

[anon]

It displays the contents of those two registry entries. I need them to create an updated TLS Fix.reg file that will let the mod work fine on HTTPS trackers. You may have to open the Command Prompt window as administrator for the second command to work.

Note that you must "go to your Internet Settings [and] disable SSL 3.0 and enable all versions of TLS up to 1.3" first. I think SSL 3.0 is disabled by default these days, but I'm not sure about the latter, as it's only recently been added to Windows.

[sashiagustina]

The latest one rearranged interface elements after more than a decade, and I don't want to "relearn" the program. The old version works fine in any case.

oh yeah, is it the same reason so many trackers out there, recommend older version of some clients rather than newer version ?

---------- Post Merged at 11:44 ---------- Previous Post was at 11:39 ----------

It displays the contents of those two registry entries. I need them to create an updated TLS Fix.reg file that will let the mod work fine on HTTPS trackers. You may have to open the Command Prompt window as administrator for the second command to work.

Note that you must "go to your Internet Settings [and] disable SSL 3.0 and enable all versions of TLS up to 1.3" first. I think SSL 3.0 is disabled by default these days, but I'm not sure about the latter, as it's only recently been added to Windows.

i will do it, and how i upload the reg file? SSL 3.0 disabled by default, yes

first command result
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings
SecureProtocols REG_DWORD 0x2a80

second command result
does not show anything

[anon]

oh yeah, is it the same reason so many trackers out there, recommend older version of some clients rather than newer version ?

No, that's rather related to how accurately they report traffic and adhere to the protocol and enhancement specifications.

first command result
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Internet Settings
SecureProtocols REG_DWORD 0x2a80

second command result
does not show anything

Excellent, thank you. 0x2A80 is the value I expected for SecureProtocols, but I wanted to be sure. As for the other one, getting no results is a possible outcome, but just to confirm, did you run it as administrator?

[sashiagustina]

No, that's rather related to how accurately they report traffic and adhere to the protocol and enhancement specifications.



Excellent, thank you. 0x2A80 is the value I expected for SecureProtocols, but I wanted to be sure. As for the other one, getting no results is a possible outcome, but just to confirm, did you run it as administrator?

i did run it as admin, something wrong with my pc ?

[anon]

something wrong with my pc ?

No, as I said it's possible for the key to be empty.

Anyway, with this, I already have the .reg file for the upcoming version ready. Thanks for your cooperation!

[sashiagustina]

No, as I said it's possible for the key to be empty.

Anyway, with this, I already have the .reg file for the upcoming version ready. Thanks for your cooperation!

you are welcome :)

[anon]

New version is up. Any interest on the following features?

• DHT patch that allows using DHT, PEX and LPD on private torrents, but does not enable them by default.
• /LARGEADDRESSAWARE patch that allows uTorrent to use 4 GB of memory under 64-bit Windows, and more than 2 GB on 32-bit systems if PAE and USERVA are enabled. The disk cache size is still limited to ~2 GB. Stability is not guaranteed, but posts in the official forum suggest it is greatly improved under high-demand scenarios (e.g. seeding thousands of torrents).
• rss.update_interval patch that allows setting values below 5.

[alina]

To me, v3 has a faster download speed than v2, more peer connections too, but some private trackers only allow v2. Also, v3 has better support for the 4K display. V2 is really starting to show its age.

[anon]

I've been using uTorrent since version 1.3, and can confidently say 2.2.1 was the pinnacle in terms of interface design. However, it is over a decade old, has several known bugs and security vulnerabilities, and can't handle big .torrent files or piece sizes. Hardcore users will disagree, but I strongly advice against using it. A P2P client has to be exposed to connections from random hosts all over the Internet by definition, so this isn't a "be careful and you'll be fine" situation.

[anon]

The thread and attachment were mislabeled The new version was build 45838, latest stable one at the moment. I have just corrected it everywhere.

[anon]

Okay, last reupload for now, I promise. I went all-out with the mods, since they seemed useful and stable enough.

Changelog

• Fixed "invalid URL" error
• Added DHT Patch v2: allows the use of DHT, PEX and LPD for private torrents, but does not enable them by default
• Added /LARGEADDRESSAWARE patch: allows the process to use up to 4 GB of RAM on 64-bit systems, or up to 3 GB on 32-bit systems configured to support it (PAE and USERVA > 2048). The disk cache is still limited to 1800 MB
• Added rss.update_interval patch: allows values lower than 5
• Wiped PE timestamp because I can
• Added a new splash screen to the first post

Note: the DHT patch will not apply for pre-existing torrents. To make that happen, you need to edit the resume.dat file with BEncode Editor and set their "dht" value to 13 (allowed, DHT and PEX enabled), 1 (allowed, DHT enabled) or 0 (allowed, both disabled); for Local Peer Discovery, set "lsd" to either 8 (allowed, enabled) or 0 (allowed, disabled).

[JohnWick]

i tried to download a torrent from private tracker by this version,

all my download data was wasting, it was showing in hash fail, wasted..
i downloaded it succesfully with old version

i think old utorrent 2 versions are good, than new