BiglyBT Extreme Mod by SB-Innovation 2.3.0.0 Beta

So @DigitalDJ I've tried every troubleshooting measure you've proposed. Currently my main concern is if you are actually listening to any kind of negative feedback, or if you just don't understand the problems highlighted by JP2020.
After trying various solutions you've recommended to solve Perfect Spoof not working on HDBits and and BitHDTV is still showing me as a leecher with my BT client being BiglyBT 2.3.0.0 instead of qBitTorrent 4.2.1
Thank you very much for your efforts to solve this problem but you don't seem to understand that we are trying to report whats not working to actually move ahead in this discussion.

As for any installation issues: I haven't had any JP2020, despite reinstalling it numerous times

Quote:

---

Originally Posted by --->HDBD<---

As for any installation issues: I haven't had any JP2020, despite reinstalling it numerous times

---

Thanks for that. So my installation issues would seem likely to be unrelated to the client_id problem

What you might try is changing the version spoof using the contents of BiglyBTSpoof.properties if Azureus isn't banned - it should disable the GF spoofs anyway - but check that no spoofed fields 'hangover'


#BiglyBT / Vuze / Azureus Perfect Spoof ;)
#By Shu
#No check are being done on what's entered !
#Enter valid version numbers otherwise you'll be detected as Unknown/Fake client
#Example :
#2.5.0.4
#3.0.2.2
#3.0.2.3_B11
#To activate it write azureus.spoof.boolean=True
#To deactivate it write azureus.spoof.boolean=False
#Spoof BiglyBT azureus.spoof.spoofbiglybt=True
#Spoof Azureus / Vuze azureus.spoof.spoofbiglybt=False
azureus.spoof.boolean=True
azureus.spoof.spoofbiglybt=False
azureus.spoof.value=5.7.5.0


When i tried it showed in the tracker as Azureus (version)





Could i ask you to clarify what you actually did being as the first 'install java' instruction is under such confusion, and if you did anything other than simply run the BBT installer linked as step to? and if you had/have a java installed?
Might help me see whats going wrong.







Regarding my issues, and for info
https://github.com/BiglySoftware/BiglyBT/issues/583

maybe Need to try the version there but need to look up what the 1.8 vs 13.2 etc version numbers mean.


Does seem like installing jre rather than jdk makes little if any actual difference.


Seems to be less glitches like magnets giving a similar java library error (but working OK as copy link into open works fine) if java installed before BBT install rather than after for me with openjdk. No idea why, and not ceratin install sequence is the cause/fix.


'the procedure entry point ucrtbase.terminate could not be located in the dynamic link library
api-ms-win-crt-runtime-i1-1-0.dll'


Thought i had remembered what I did the one time the client_id worked ok, but perhaps not. Its still showing biglybt (version)
- maybe it was just a fluke or wishful thinking.

Quote:

---

Originally Posted by --->HDBD<---

So @DigitalDJ I've tried every troubleshooting measure you've proposed. Currently my main concern is if you are actually listening to any kind of negative feedback, or if you just don't understand the problems highlighted by JP2020.
After trying various solutions you've recommended to solve Perfect Spoof not working on HDBits and and BitHDTV is still showing me as a leecher with my BT client being BiglyBT 2.3.0.0 instead of qBitTorrent 4.2.1
Thank you very much for your efforts to solve this problem but you don't seem to understand that we are trying to report whats not working to actually move ahead in this discussion.

As for any installation issues: I haven't had any JP2020, despite reinstalling it numerous times

---

As I've said multiple times. There may very well be a problem with PerfectSpoof. I haven't had time to really had a deep look into it.

The installation issue that JP2020 has absolutely nothing to do with the potential issue.

To help track down the issue, as I've recommended previously: Install Wireshark, packet capture a HTTP tracker update with PerfectSpoof enable, and share the results. Happy for you to censor any private information -- torrent hashes, pass hashes etc.

Here a capture
Attachment 20323

Thank you, this is actually extremely useful. I'll look into it as soon as I can.

Alright, today I took the time to do a completely clean install, following the procedure in the first post, just as if I'd never used the mod before. It worked. There are no error messages, it runs, the spoof works, "stop torrent when completed" works, everything is fine. So JP2020, I honestly have no idea what's causing you so much trouble here. But you're welcome to try running the mod using the script I posted before; actually, please use this slightly modified one instead.

Code:

---

*removed*

---

Then open the mod using that as a replacement for BiglyBT.exe. This has to work regardless of whether you have zero, one or more runtimes of any version already installed anywhere or whether they are operational or not... but well, the same should be true of the executable (and it was during my tests).

HDBD, that screenshot is pretty interesting, because everything other than the User-Agent is as it should be for qBittorrent 4.2.1. So the spoof isn't completely broken (which makes this even more puzzling).

First of all, it should be noted that as of this writing, there are three spoofing features in this mod.

1. Perfect Spoof 2 by ghostfucker, which is the flagship one
2. Shu's Perfect Spoof, controllable via a .properties file. Backported from the Legitbly mod but not really relevant here
3. The Client Identification plugin included in the official BiglyBT

No. 2 is not a problem as long as left disabled. My guess is that the third one is interferring with the first under certain configurations or conditions, but once again, I have been completely unable to reproduce that during testing. Please try the following.

• Stop all torrents, disable ghostfucker's Perfect Spoof and close the mod.
• If by any chance you edited BiglyBTSpoof.properties, replace it with an unmodified copy.
• Open the mod. Don't start any torrents, but open the Options panel and make sure that...
  
  Tracker -> Client: "Send Java version and OS name" is enabled (the default).
  Plugins -> Client Identification: Client is set to "BiglyBT 2.3.0.0" (the default).
  Plugins: "bgclientid" is unticked.
• Restart the mod. Enable ghostfucker's Perfect Spoof and pick the client you want. Restart again.

With those settings, it works fine for me. Verified with Wireshark on Pornolab (HTTP tracker) and IPTorrents (HTTPS, but shows your User-Agent on the torrent list), tested spoofing both uTorrent and qBittorrent.

Quote:

---

Originally Posted by anon

HDBD, that screenshot is pretty interesting, because everything other than the User-Agent is as it should be for qBittorrent 4.2.1. So the spoof isn't completely broken (which makes this even more puzzling).

First of all, it should be noted that as of this writing, there are three spoofing features in this mod.

1. Perfect Spoof 2 by ghostfucker, which is the flagship one
2. Shu's Perfect Spoof, controllable via a .properties file. Backported from the Legitbly mod but not really relevant here
3. The Client Identification plugin included in the official BiglyBT

No. 2 is not a problem as long as left disabled. My guess is that the third one is interferring with the first under certain configurations or conditions, but once again, I have been completely unable to reproduce that during testing. Please try the following.

• Stop all torrents, disable ghostfucker's Perfect Spoof and close the mod.
• If by any chance you edited BiglyBTSpoof.properties, replace it with an unmodified copy.
• Open the mod. Don't start any torrents, but open the Options panel and make sure that...
  
  Tracker -> Client: "Send Java version and OS name" is enabled (the default).
  Plugins -> Client Identification: Client is set to "BiglyBT 2.3.0.0" (the default).
  Plugins: "bgclientid" is unticked.
• Restart the mod. Enable ghostfucker's Perfect Spoof and pick the client you want. Restart again.

With those settings, it works fine for me. Verified with Wireshark on Pornolab (HTTP tracker) and IPTorrents (HTTPS, but shows your User-Agent on the torrent list), tested spoofing both uTorrent and qBittorrent.

---

I suspect it is indeed the Client Identification plugin. It does indeed include code to add a User-Agent to tracker requests. Although, I'm still going to work through all the patches we apply and ensure they're been applied in the correct locations.

Honestly, they should get rid of that already. It's no longer necessary - the transition stage is over, BiglyBT is the new Vuze - and trackers are always going to frown upon a client that has ID spoofing features out of the box. Even if the intentions behind it are good and it only allows a very limited set of choices.

Quote:

---

Originally Posted by anon

Honestly, they should get rid of that already. It's no longer necessary - the transition stage is over, BiglyBT is the new Vuze - and trackers are always going to frown upon a client that has ID spoofing features out of the box. Even if the intentions behind it are good and it only allows a very limited set of choices.

---

AFAIK, they did remove it in 2.3.0.0, but I specifically reverted that commit to keep the plugin. I'm interested as to why it's now causing problems...or maybe it was always a thing. I still need to confirm whether that is actually the issue.

---------- Post Merged at 20:52 ---------- Previous Post was at 16:00 ----------

HDBD, can you please elaborate more on your setup. I just reviewed the code and things look OK. I personally tried a HTTP tracker and confirmed the qBT 4.2.1 spoof works.

I'm curious as to why in your About Window it says "N/A" under Java 13.0.2. It should be "Oracle Corporation". This is probably a red herring.

Can you:

- screenshot your full Extreme Mod settings
- open a command prompt and post the output of the following:
cd "C:\Program Files\BiglyBT\jre\bin"
java -XshowSettings:properties -version
- Mention if any trackers for which you find PerfectSpoof works?
- share the sources tab for a torrent (censor hostnames, and any other sensitive info)?
- list the contents of:
%APPDATA%\BiglyBT\plugins
%PROGRAMFILES%\BiglyBT\plugins
- share the "Connections" tab in BiglyBT settings
- the contents of %PROGRAMFILES%\BiglyBT\BiglyBTSpoof.properties

@DigitalDJ

Could you please provide the attachment to those of us who do not care about spoofing at all?
All I need is "no upload" and automatic removal after finish. I couldn't care less about spoofing.

2.2.0.2 Beta is a mess for me. Automatic removal is completely broken and it has just crashed and corrupted its settings for the second time in 24h. I'd like to at least try and see if 2.3.0.0 works better.

Thank you very much for your hard work.

@DigitalDJ

I don't have too much time right now.
about weekends i will inform more

I just cleaned up the thread of "where's the download link" posts, and rolled the sticky and announcement lists back to 2.2.0.2 until we can reupload this version.

1. I don't know why it was shown as N/A but now it looks like
Attachment 20329

2. Here are the Extreme Mod settings
Attachment 20330
Attachment 20331

3. java -XshowSettings:properties -version

Quote:

---

Microsoft Windows [Version 10.0.18363.720]
(c) 2019 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\xxxxxxx>cd "C:\Program Files\BiglyBT\jre\bin"

C:\Program Files\BiglyBT\jre\bin>java -XshowSettings:properties -version
Property settings:
file.encoding = Cp1252
file.separator = \
java.class.path =
java.class.version = 57.0
java.home = C:\Program Files\BiglyBT\jre
java.io.tmpdir = C:\Users\xxxxxxx\AppData\Local\Temp\
java.library.path = C:\Program Files\BiglyBT\jre\bin
C:\WINDOWS\Sun\Java\bin
C:\WINDOWS\system32
C:\WINDOWS
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler
C:\Program Files (x86)\Intel\iCLS Client\
C:\Program Files\Intel\iCLS Client\
C:\WINDOWS\system32
C:\WINDOWS
C:\WINDOWS\System32\Wbem
C:\WINDOWS\System32\WindowsPowerShell\v1.0\
C:\WINDOWS\System32\OpenSSH\
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files\Intel\Intel(R) Management Engine Components\DAL
C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT
C:\Program Files\Intel\Intel(R) Management Engine Components\IPT
C:\Program Files\IDM Computer Solutions\UltraEdit
C:\Program Files\IDM Computer Solutions\UltraCompare
C:\Program Files\PuTTY\
C:\Program Files\ojdkbuild\java-13-openjdk-13.0.1-2\missioncontrol\
C:\Program Files\ojdkbuild\java-13-openjdk-13.0.1-2\bin
C:\Users\xxxxxxx\AppData\Local\Microsoft\WindowsAp ps

.
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 13.0.2+8
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 13
java.vendor = Oracle Corporation
java.vendor.url = https://java.oracle.com/
java.vendor.url.bug = https://bugreport.java.com/bugreport/
java.version = 13.0.2
java.version.date = 2020-01-14
java.vm.compressedOopsMode = Zero based
java.vm.info = mixed mode, sharing
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 13
java.vm.vendor = Oracle Corporation
java.vm.version = 13.0.2+8
jdk.debug = release
line.separator = \r \n
os.arch = amd64
os.name = Windows 10
os.version = 10.0
path.separator = ;
sun.arch.data.model = 64
sun.boot.library.path = C:\Program Files\BiglyBT\jre\bin
sun.cpu.endian = little
sun.cpu.isalist = amd64
sun.io.unicode.encoding = UnicodeLittle
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = Cp1252
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level =
sun.stderr.encoding = cp850
sun.stdout.encoding = cp850
user.country = LI
user.dir = C:\Program Files\BiglyBT\jre\bin
user.home = C:\Users\xxxxxxx
user.language = de
user.name = xxxxxxx
user.script =
user.variant =

java version "13.0.2" 2020-01-14
Java(TM) SE Runtime Environment (build 13.0.2+8)
Java HotSpot(TM) 64-Bit Server VM (build 13.0.2+8, mixed mode, sharing)

C:\Program Files\BiglyBT\jre\bin>

---

4. On This Tracker PerfectSpoof works
Attachment 20332

5. %APPDATA%\BiglyBT\plugins
Attachment 20333

6. %PROGRAMFILES%\BiglyBT\plugins
Attachment 20334

7. %PROGRAMFILES%\BiglyBT\BiglyBTSpoof.properties

Quote:

---

#BiglyBT / Vuze / Azureus Perfect Spoof ;)
#By Shu
#No check are being done on what's entered !
#Enter valid version numbers otherwise you'll be detected as Unknown/Fake client
#Example :
#2.5.0.4
#3.0.2.2
#3.0.2.3_B11
#To activate it write azureus.spoof.boolean=True
#To deactivate it write azureus.spoof.boolean=False
#Spoof BiglyBT azureus.spoof.spoofbiglybt=True
#Spoof Azureus / Vuze azureus.spoof.spoofbiglybt=False
azureus.spoof.boolean=False
azureus.spoof.spoofbiglybt=True
azureus.spoof.value=2.3.0.0

---

Thanks, can you also share the Sources tab for a tracker that you think PerfectSpoof does not work for?

This is puzzling. Cheers