Vuze Extreme Mod by SB-Innovation 5.0.0.1_B06 Beta

[DigitalDJ]

SB-Innovation Presents

Vuze Extreme Mod by SB-Innovation 5.0.0.1_B06 Beta



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

>>>>>> DigitalDJ & ghostfucker <<<<<<


╔═══════════════════════════╗
Credits:
╚═══════════════════════════╝

>>>>>> Butcho <<<<<<
>>>>>> Rebound <<<<<<
>>>>>> hitman <<<<<<
>>>>>> Manas <<<<<<
>>>>>> eudora <<<<<<
>>>>>> ghostfucker <<<<<<
>>>>>> anon <<<<<<
>>>>>> Instab <<<<<<

╔═══════════════════════════╗
Supplied by:
╚═══════════════════════════╝

>>>>>> SB-Innovation <<<<<<

╔═══════════════════════════╗
Original Mod by:
╚═══════════════════════════╝

>>>>>> Shu <<<<<<


Change Log:

+ Perfect Spoof 2
+ uTorrent ID Generator
+ Modifiable Client Files
+ Ghostleech
+ LTEP Fixes
+ Multiple peerlist entries fixed
+ More No Report Options
+ Perfect Spoof 1.0 by ghostfucker
+ (Fake Upload) Stop faking when swarm speed is zero
+ Upload Kicker
+ Ratio Tool
+ Fixed bug preventing Vuze plugin downloads
+ Synced with latest Shu Mod
+ (Upload Multiplier) Show as seeder
+ (SBI-Hack Torrentview) Scrollbars added
+ Use Swarm Peers fixed
+ Updated core to Vuze 5.0.0.1_B06


Vuze Change Log:
Vuze Change Log

Installation:
1. Download and install Vuze (if this is a Beta/CVS update, download the latest NON BETA release) (Vuze : Java BitTorrent Client - Download).
2. BACK UP YOUR TORRENT LIST! IT IS LIKELY YOU WILL LOSE IT!
3. Optional: If you want to make a backup of your old Vuze version. Go to the install directory and rename Azureus2.jar to Azureus2.jar.bak
4. Extract the files using WinRAR (WinRAR archiver, a powerful tool to process RAR and ZIP files) or equivalent to %PROGRAMFILES%\Vuze (C:\Program Files\Vuze) and overwrite ALL files.
5. Run Vuze and Enjoy!
NOTE: For other operating systems simply replace the Azureus2.jar. For 64-bit, portable, and Vuze Plus support read the README in the appropriate package.

Troubleshooting:
Before posting problems please make sure:
1. You have updated Java Runtime Environment (JRE) to version 6 (Java SE Downloads).
2. You have removed the Vuze folder in %PROGRAMFILES% (C:\Program Files\Vuze).
3. You have removed the Vuze folder in %APPDATA% (The folder may be hidden).
C:\Documents and Settings\<username>\Application Data\Vuze for XP
C:\Users\<username>\AppData\Roaming\Vuze for Vista
4. Reinstalled Vuze using the package from Vuze : Java BitTorrent Client - Download
5. Re-applied the hack from the downloaded archives.

Warning: Performing steps 2 and 3 will wipe your torrent list and Vuze settings.

Enjoy!

[anon]

That's interesting. Closer inspection reveals that 81EA in hex = 1000000111101010 in binary. But 0000000111101010 in binary = 490 decimal.

Sign bit - Wikipedia, the free encyclopedia

Looks like they were setting the sign bit to 1 (negative) for some reason.

[The248]

That happens in builds lower than 10054.
Don't really know why, it just does.
By the way that's the same as adding 32768 to the build number and then converting it to hex, 32768 + 490 = 33258 = 81EA in hex

[Lucius]

As i Said before I just ignore the 1 and I work on the second part xD I can say it's 100% perfect but it did work with a lot of tries .

[quertiy]

Isn't perfect spoof 2 integrated into to latest vem, along with the "latest" utorrent client file? If yes, why is the example of pefectspoof2 client attached in te op so different from the actual utorrent client that comes with the latest vem?

[anon]

The ones included PerfectSpoof2_Docs.zip are samples. They're useless per se; if you open them you will see that they only contain empty values and comments. You're supposed to fill that in with the information captured from the client you wish to emulate, if writing an emulation from scratch.

[quertiy]

I understand that. What I don't understand is if the "3.1.0 (26616).client" that comes with the latest version of vem emulates everything that can be emulated. In the pefectspoof2 samples I see information about scrape emulation, which is not used in the "3.1.0 (26616).client". So, "3.1.0 (26616).client" doesn't emulate everything that can be emulated, so the spoof isn't perfect right? If vuze's default scrape settings, announce period settings are not the same as utorrent's defaults (and I don't think they are), someone could begin suspecting something. Am I mistaken? I mean, yes, the Utorrent's ID is emulated but everything else behaves like vuze, and if someone figures that out they could know I'm using the mod, or at least, suspect it.

[anon]

In the pefectspoof2 samples I see information about scrape emulation, which is not used in the "3.1.0 (26616).client".

That's to disable scraping when emulating clients that do not support it (e.g. BitTornado), or give it special treatment like sending different HTTP headers. If that section is not present, scraping is allowed and uses the same behavior as tracker announces to send requests, which is fine for uTorrent.

<!-- Scrape settings, OPTIONAL (Default: Same settings as in announce specified) -->

[quertiy]

Is there a way to fake until a certain ratio and then stop the faking system and let the torrent announce the real upload?

[anon]

http://www.sb-innovation.de/showthre...threadid=13781

Options 17c and 17g.

[quertiy]

latest utorrent's peer id

-UT3310-%3ft%2c%2f%a1%01U0Z%87%96%2b

1.
1.6.1 client has

isEncodingDisabled="true"

3.1 client has not
how do I know if 3.3.1 needs this line or not?

2.
what is

<reservedBytes>

and how do I find it's value

3.
how many characters are in the prefix?

4.
do I need

ipType="2" ipMode="1" ipFallBack="0"

<param>[corrupt]</param>

<param>&amp;ipv6={ip}</param>

<field>Connection: Close</field>

5.
How do I know that the latest uTorrent build doesn't need additional parameters to be emulated in order to blend in with the crowd?

edit: http://www.ghacks.net/2012/09/22/uto...ring-sessions/

[anon]

1. I think that was related to how the LTEP handshake was sent, newer builds sending additional information in bencoded format, but I don't remember the specifics so I'll let ghostfucker reply this one.
2. http://www.sb-innovation.de/showthre...104#post288629
3. it's not about characters, but bytes. uTorrent's prefix has 12 bytes, the -UTxxxx- part plus two static ones that define the build number, as discussed in the last page. Stuff that looks like %xx (that is, a percent sign followed by two characters) is one byte, not three, because it's URL-encoded. In your example above, the prefix would be -UT3310-%3ft
4. they wouldn't be there if they weren't required. As a general rule, the addition of new params or HTTP headers is rare, but can happen (and effectively has since 1.6.1). Also, if you for example don't have IPv6 installed in your computer, the ipv6 parameter won't get sent, but that doesn't mean you have to remove it. Vuze will emulate that same behavior (that particular one is defined by ipType, Mode and Fallback), and a client file should account for all possibilities.
5. well, you use a packet sniffer to capture the data the new build sends to the tracker and peers, and note any significant changes

[ghostfucker]

1.6.1 client has

isEncodingDisabled="true"

there is a bug in ut 1.5 till 1.6.1. they didn't encode the µ in the handshake.

[starice]

I found out by a youtube video how to exacly use this mod the easy way.
I use the fake ratio cheat for each torrent and i set it between 1.0/2.5.
Now every torrent gets cheated and i don't need to cheat big chunks of upload like i used to do with Trackerpro.
This is so FINE.. And i'am so thankfull for this mod.. BAd thing is vuze sucks as a client but anyway good job on the mod.

[anon]

Just remember that the easiest way isn't always the best one.

[starice]

Yes, my account got disabled because i jumped on a fresh posted torrent.
What is the best way to cheat using this mod?