[Tutorial about the BiglyBT Extreme Mod] All settings explained

[grebetu]

spoofing is dangerous.. a lot of trackers can detect that and, anyway, why do you need the EXTRA risk? without spoofing is already risky.. what's the problem you'll be seen as Vuze client?

Vuze client is suspicious by itself, I've been spoofing uTorrent in all major trackers and haven't been detected yet, can you elaborate what trackers detect spoof?

[enemy]

can you elaborate what trackers detect spoof?

ScT was one of them. Which means, that there are some (detectable) bugs.

[saebrtooth]

spoofing is dangerous.. a lot of trackers can detect that and,

Can you give us some proof that trackers have detected Vuze Exteme Mod (VEM) spoofing?

ghostfucker spoofs exactly the same output as the real client when communiating with the tracker, so how can that be detectable?

anyway, why do you need the EXTRA risk? without spoofing is already risky.. what's the problem you'll be seen as Vuze client?

VEM is not the original client, its a mod of the original Vuze client. If everyone using the mod shows it as the same client then it just raises the chances that VEM would be found out. If the tracker sees that there are different clients (spoofs) connecting this just makes it harder for them to guess that a hacked client is being used. ie by calculating statistics not detection of a hacked client

ScT was one of them. Which means, that there are some (detectable) bugs.

Maybe you can elaborate a bit futher. What client spoof did you use and what were the settings did you use that you say banned you?

[dreamer]

I guess I'm a bit outdated then.
I tried spoofing when the Shu hack was still early and got banned on a few trackers.
never took the chance since.

[Instab]

ScT was the only site that could detect the ut spoof but never heard of issüs with other sites.
a current vuze mod with ghostfucker's spoof should be fine.
and depending on the whitelist you could also try the vuze mod without any spoof at all

[anon]

spoofing is dangerous.. a lot of trackers can detect that and, anyway, why do you need the EXTRA risk?

12:59 11/02/2010: memcached HIT

Well, let's see:

One of the Hack's biggest weaknesses is was that it has had to identify itself as Azureus, and can could perfectly spoof only other versions of it so far. Because of this, tracker admins can could keep an eye on everyone using "Azureus", which means you'd have to be more careful, or even ban that client, and make it harder for you to use it there.

With the Extreme Mod, this limitation is gone - you have a bunch of other clients and versions you can 100% undetectably spoof, both to tracker and peers. ... any peer on a torrent could be a Hack user, as you'll be able to emulate BitTornado, Deluge, Halite, the Mainline client, and one of the biggest archievements of this Mod - uTorrent, which was thought to be impossible to spoof, apart from of course Azureus itself.

[pillow]

i have a problem with 4.3.1.4 .
no idea if it was also with former builds.

whenever i try to re-add torrentfiles in order to seed them, vuze doesnt recognize them anymore.
e.g. i downloaded a dvd (vobs) a while ago, now i redownloaded the original .torrent and pointed it the the right directory. instead of re-hashing the old files, i got 0-byte files (same name as the originals) with the .az! extension. so obviously vuze doesnt recognize the old ones.
the same happens when i make a new torrent for uploading, reload the .torrent file from the website and point it to the dir with the originally hashed files, but the same, vuze doesnt recognize them and creates copies of them with .az! ..??
when i use e.g. utorrent with the same .torrent and pointing to the directory mentioned above, it re-hashes and seeds without a problem.

anyone noticed that? is this a known error?

[anon]

Try deleting the torrents folder and downloads.config file from the settings directory and seeing if the problem persists. This will wipe the torrent list, of course, so you may want to back it up.

[pillow]

did it, +downloads.config.bak . the list was empty, added the .torrent again and pointed it to the original dir, the same, only .az! copies...

[anon]

Well, then you should put the files back and try it with the official Vuze. If it doesn't happen, it's a mod bug - if it does, it's an official one, and they should get it fixed soon.

[PO1]

I have question
It is posible start two client Azureus 3052 and Vuze 4311 ??
uTorrent it is posible but Vuze i dont know :(
please answer

[anon]

-Dazureus.config.path= Sets the dir Azureus uses for config files and plugins. Default config path is OS-dependant: Under unix, this usually is ~/.azureus/; under Windows, this usually is %appdata%\Azureus\; Under Mac OS X, this usually is "/Users/<username>/Library/Application Support/Azureus/".
combine with -DMULTI_INSTANCE=true to open multiple instances of Azureus.
Note: opening multiple instances of Azureus is generally a very bad idea, except in very special circumstances.
The multi-instance flag can be used to disable the instance-checking if some other application is listening on port 6880 and prevents Azureus from starting.
-Dazureus.install.path= sets the install path for Azureus, this is useful if you want to override where Azureus places its shared plugins.
Note: this settings should be used with care as it can break the auto update feature

Commandline options - VuzeWiki

Remember the single EXE version of the Extreme Mod can't take command-line parameters directly, you must use the Azureus.l4j.ini file to pass them.

[fakeking]

Anon, I've seen your post about cross-seeding.

But I can't manage to make VEM preseed the torrent. It always search for the real files in my
HDD, pal.

[anon]

But I can't manage to make VEM preseed the torrent. It always search for the real files in my
HDD, pal.

Did you add it to the same folder as stopped, and then did the hash check?

[fakeking]

So, I need to downloading some pieces to make it "fake files" then stopped, remove torrent and finally added the torrent again as seeding only.

Is it right, pal??.