[Tutorial about the BiglyBT Extreme Mod] All settings explained

[molosse]

It looks key type should be hex instead of anum, then. You can remove the charSet, as Vuze defaults to 0-9 and uppercase A-F if type is hex, and that's just what we need.

Hi,
by "remove the charSet", do you mean to remove this line:
<key type="anum" length="6" />
or maybe use:
<key type="hex" length="6" />; just to be sure the key is still 6 digit.

What about requirecrypto? Did you see that during testing?

nope, never seen that one in the QBT real client.

cheers

[anon]

The key section in the 3.3.5 client file you posted looks like this:

	<key type="hex" length="8" isGlobal="true">
		<charSet>0123456789abcdef</charSet>
	</key>

The chatSet block, highlighted above, should be removed.

[molosse]

The key section in the 3.3.5 client file you posted looks like this:

	<key type="hex" length="8" isGlobal="true">
		<charSet>0123456789abcdef</charSet>
	</key>

The chatSet block, highlighted above, should be removed.

Hi,
I removed the charSet and it fixed the Key parameter

I did notice another difference (I didn't see before but it was always there)

for the info_hash, the legit client only use letter without capitalization, while VEM use both with and without.

legit:
4%ad.d%fc%ba8j%1c%26%f7%7f%1d%c1%bb%d2u%05%7f%0f
Fake:
4%AD.d%FC%BA8j%1C%26%F7%7F%1D%C1%BB%D2u%05%7F%0F

Can I influence that in the client file?

[anon]

Sure, just change the following part of your client file:

		<infoHash exceptions="!()*-._~" />

To add this parameter:

		<infoHash isLowerCase="true" exceptions="!()*-._~" />

[molosse]

Hello,

So I'm now confident I have the perfect spoof Qbitorrent client spoof file. I sniffed around 300 connections with smartsniff the last 2 weeks and I now have perfect match (when applicable) between the spoof and the real Qbitorrent.

Some comment about encryption:
Setting the encryption in Vuze settings does not reflect in the announce, so if you need or wish to force or just support encryption, you have to hard code the parameter in the spoof file.

As such; I attached a ZIP file that contains 3 client files to support the 3 different encryption levels.

their file name should be self-explanatory.

1. 3.3.5 with Preferred Crypto.client
2. 3.3.5 with Required Crypto.client
3. 3.3.5 without Crypto.client

file 1 will add supportcrypto=1 in the announce
file 2 will add requirecrypto=1 in the announce
file 3 will not add any crypto parameter in the announce.

I tested the 3 files. In terms of connected peers, file 1 and 3 let connect the same number of peers, some peers have encryption, some don't. With file 2, VEM only allow peers with encryption enabled.
I suggest to use file 1. Theoretically it's the setting that gives the highest number of possible peers.
This has worked fine for me on trackers like PTP, HD-T, HDO, WiHD, WFL.

Anon,
Feel free to add this Zip in the Member section along with all client files are.

Thanks again for the help.

[anon]

I tested the 3 files. In terms of connected peers, file 1 and 3 let connect the same number of peers, some peers have encryption, some don't. With file 2, VEM only allow peers with encryption enabled.

I'm guessing this is a side effect of your encryption settings, rather than the parameters sent by Vuze to the tracker.

The post was copied to the member section, thanks!

[molosse]

latest version attached, (checked with smartsniff)
feel free to add the file to the Member section, if you wish so.

[molosse]

Hi there,

I'd like to report a behavior that I think is a risk and could help a tracker to identify a cheater!

Install Vuze.
go to Tools -> Options
go to Mode and activate advanced mode
go to Tracker -> Client
In the "information" block, you can see that "Send Java Version and OS Name" is selected and you have the option to unselect it.
Install VEM

go back to Tracker -> Client
In the "information" block, you can see that "Send Java Version and OS Name" is still selected but it is now read-only and cannot be selected.

so what?

I don't know for sure, but on a tracker of mine, I see on my profile this info:

Clients: qBittorrent v3.3.5;Windows Server 2012 R2;Java 1.8.0_9

Here, qBittorrent v3.3.5 is spoofed by VEM

Now I repeat everything with a new account on a different PC but this time:
Install Vuze
go back to Tracker -> Client, unselect the "Send Java Version and OS Name"
install VEM
go back to Tracker -> Client, "Send Java Version and OS Name" is still unselected and can still not be changed.
I launched 2 torrents on 2 bittorrent clients and the next day I checked my profile and I see:

Clients: qBittorrent v3.3.7; Deluge 1.3.12

Here, qBittorrent v3.3.7 is spoofed by VEM, Deluge is legit.

"Send Java Version and OS Name" has been discussed elsewhere and it was recommended to turn it off.
in a future version of VEM, could you please let us change that "Send Java Version and OS Name"?

[push3r]

Hi,

Awesome forum! First post!

I would like to be a streamlined cheater . I have been using VEM to do real downloading, ghostleech, and trying to get the speed++ seeding to work but running out of troubleshooting lucks.

When I use VEM with the speed++ / show as seeder 100%, it doesn't do anything to the tracker and that the fake up speed is zero all the time. The torrent is quite healthy with around 200 seeders / 50 leechers.

When I switch to mRatio or RMP on the same torrent, it starts fake uploading immediately and can see myself on the tracker snatchlist with my ratio, amount uploaded, and speed updating.

Do I really need to correctly configure port forwarding for VEM to function properly? Before I even messed around with my firewall's port fowarding, mRatio and RMP worked right out of the box. Anyhow, I went ahead and configured port fowarding to point to my VEM box; additionally, I opened the torrent port on the Windows firewall. I restarted VEM and still no luck. Sometime it would start fake uploading for a few seconds and then nothing.

On VEM, for fake upload/seeding, do i really need to connect to the peers? As of right now, no peers can connect to me. I even used the Ubuntu torrent to do the "show as seeder 100%" and no peers or seeders could connect to me and it's not doing any fake uploading.

I am stumped. What am I missing here? I like mRatio and RMP, but I would like to streamline my cheating experience. BTW, I am using the uTorrent perfect spoof on VEM not sure if that matters.

Thank you!

[anon]

See point 12a in the first post. That setting is the bane of all newcomers who cannot seem to understand why fake upload never increases. mRatio and RM+ don't connect to peers, so while they have a similar setting, it's neither as reliable nor enabled by default.

Port forwarding has little to do with this, but you should always make sure you're connectable anyway. It's good P2P practice.

[push3r]

See point 12a in the first post. That setting is the bane of all newcomers who cannot seem to understand why fake upload never increases. mRatio and RM+ don't connect to peers, so while they have a similar setting, it's neither as reliable nor enabled by default.

Thank you anon! I get it now. VEM is one complicated beast for newcomers for sure. I have spent almost a week soaking in all the relevant info from forum and am getting there.

That setting in 12a is not so obvious especially if one is not experienced with cheating and or torrenting in general. I scratched my head why mratio and rmp worked immediately but now with VEM, I set 12a to zero and boom, VEM is cheating right out of the gate. Of course, one must keep an eye out if one disable 12a safety feature.

[anon]

One must keep an eye out if cheating in general. Options like that one reduce the risk, but are not a substitute for user interaction. There have been posts in the past from people who left Vuze faking upload overnight, or requested an "autopilot" feature. The answers are no and no, you have to be there to control things and adjust your strategy as it becomes necessary.

Anyway, welcome to the forum. I'm glad you're reading first and asking questions later and not the other way around

[molosse]

I am stumped. What am I missing here? I like mRatio and RMP, but I would like to streamline my cheating experience. BTW, I am using the uTorrent perfect spoof on VEM not sure if that matters.

Thank you!

One thing I can tell you and you don't want to streamline your cheating practice.

cheating settings shall be used according to the tracker you use. Each tracker have various tolerance to your cheating options and you should visit the tracker cheating experience forum and find your tracker to find what is better for your tracker.
Also get your spoof client 100% right.

Secondly, but I'm guessing you knew that already, practice these cheating settings with a tracker that is "easy" with cheaters (lousy or not cheating scripts) and also give as much stats on the tracker website (preferably stats per torrent).
I don't want to name any here (some might take offense and take corrective actions) but trackers are not all in the same league.

Eventually, you will find yourself bored or uncomfortable with cheating and will just enjoy the greatest feature of VEM: just be able to use Vuze on any tracker with spoofing.

[leeechy]

"Send Java Version and OS Name" has been discussed elsewhere and it was recommended to turn it off.
in a future version of VEM, could you please let us change that "Send Java Version and OS Name"?

you canchange the greyed setting, as long perfectspoof is disabled! same for tracker client peer key seperation and sending!
or disable by cmd Set Config Value=0
Tracker Client Send OS and Java Version

[molosse]

you canchange the greyed setting, as long perfectspoof is disabled! same for tracker client peer key seperation and sending!
or disable by cmd Set Config Value=0
Tracker Client Send OS and Java Version

worked like a charm, one step closer to perfection.