qBittorrent 4.3.0.1

[cloud99]

Download here:- 20772

The zip contains four files.
1) 4.3.0.1 [No support of Encryption].client
2) 4.3.0.1 [Supports Encryption].client
3) 4.3.0.1 [No support of Encryption] + [Anonymous Mode].client
4) 4.3.0.1 [Supports Encryption] + [Anonymous Mode].client

Information regarding the client:
1) Peer ID: - The Peer Id not global.
2) Key: - The key is not global.
3) IPv6:- The clients do not reports your IPv6 address. (If you want one made, please provide announces with the ipv6 enabled).
4) Encryption: - There are four client files named accordingly. Two sends the encryption parameter and the other doesn't.
5) Memory Reader: - Memory reader is not required for Peer ID and key as is not set to global. However, you can still use it to act more like the real client file but that would mean faking on only a single torrent file as BiglyBT/Vuze can only use a Custom Peer ID for an entire session and not multiple torrent within one session. The best recommendation would be to complete the torrent in your real client and then stop and remove it and then add it to BiglyBT/Vuze for seeding/ faking purposes.
7) Operating System: - Windows 10.

How to use the client files?

Simply copy and paste the client file inside the qBitorrent folder you need to make here or wherever you have installed Vuze/BiglyBT. -> C:\Program Files\BiglyBT\clientfiles\qBitorrent

How to use the correct client files?

Read post: - 358957

Session 1 [Allow Encryption]

GET /announce?info_hash=%94%a3%15%e2%cf%80%15%b2%f65%d7 %9a%abY.m%b5W%d5%ea&peer_id=-qB4301-mzlmtFlDm.7e&port=38716&uploaded=0&downloaded=0&left=2119073792&corrupt=0&key=2D2C25A9&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d1%10%1a%2b%9d%20(%11%a0%5e%8c W%c5W%a2%0b%f9t%dc%8a&peer_id=-qB4301-d8!8WX~irGm-&port=38716&uploaded=0&downloaded=0&left=2620129280&corrupt=0&key=81EC62FD&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d8%f4%84u%afF%d2%e0%1a%f1%3f%b 5%12o%06%f9b%be!%5c&peer_id=-qB4301-sn2sctqHXcNq&port=38716&uploaded=0&downloaded=0&left=903348224&corrupt=0&key=7F9AA06E&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=6%c6td%c3z%83G%8c%ef%f5I2%b5%a9 %bd%de%a66%f3&peer_id=-qB4301-YZ~Fprr~Gtcl&port=38716&uploaded=0&downloaded=0&left=884736000&corrupt=0&key=97AA6424&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

Session 2 [Require Encryption]

GET /announce?info_hash=%94%a3%15%e2%cf%80%15%b2%f65%d7 %9a%abY.m%b5W%d5%ea&peer_id=-qB4301-DgzsO.4.GHTC&port=38716&uploaded=0&downloaded=0&left=2092597248&corrupt=0&key=45E6770C&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate


GET /announce?info_hash=%d1%10%1a%2b%9d%20(%11%a0%5e%8c W%c5W%a2%0b%f9t%dc%8a&peer_id=-qB4301-aJcdjJSynIP(&port=38716&uploaded=0&downloaded=0&left=2599419904&corrupt=0&key=F21EA9F8&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate


GET /announce?info_hash=%d8%f4%84u%afF%d2%e0%1a%f1%3f%b 5%12o%06%f9b%be!%5c&peer_id=-qB4301-Nr68-BuS*nd6&port=38716&uploaded=0&downloaded=0&left=880803840&corrupt=0&key=DD9DFC81&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=6%c6td%c3z%83G%8c%ef%f5I2%b5%a9 %bd%de%a66%f3&peer_id=-qB4301-MOaO~nmkrieS&port=38716&uploaded=0&downloaded=0&left=862715904&corrupt=0&key=A947E913&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

Session 3 [Disable Encryption]

GET /announce?info_hash=%94%a3%15%e2%cf%80%15%b2%f65%d7 %9a%abY.m%b5W%d5%ea&peer_id=-qB4301-Zx6s(aTzlKTd&port=38716&uploaded=0&downloaded=0&left=2087616512&corrupt=0&key=E7431084&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d1%10%1a%2b%9d%20(%11%a0%5e%8c W%c5W%a2%0b%f9t%dc%8a&peer_id=-qB4301-trsHZr)nvA3K&port=38716&uploaded=0&downloaded=0&left=2593128448&corrupt=0&key=73A574BD&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d8%f4%84u%afF%d2%e0%1a%f1%3f%b 5%12o%06%f9b%be!%5c&peer_id=-qB4301-cE)06XzPaR3u&port=38716&uploaded=0&downloaded=0&left=876871680&corrupt=0&key=6B5A094C&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=6%c6td%c3z%83G%8c%ef%f5I2%b5%a9 %bd%de%a66%f3&peer_id=-qB4301-*WCRQnkIKrxa&port=38716&uploaded=0&downloaded=0&left=857473024&corrupt=0&key=1BECB0C8&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
User-Agent: qBittorrent/4.3.0.1
Connection: close
Accept-Encoding: gzip, deflate

Session 4 [Allow Encryption] + [Anonymous Mode]

GET /announce?info_hash=%94%a3%15%e2%cf%80%15%b2%f65%d7 %9a%abY.m%b5W%d5%ea&peer_id=-qB4301-hzTwpevEciJS&port=38716&uploaded=0&downloaded=0&left=2082897920&corrupt=0&key=59E19895&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d1%10%1a%2b%9d%20(%11%a0%5e%8c W%c5W%a2%0b%f9t%dc%8a&peer_id=-qB4301--!RJcAYX2OEi&port=38716&uploaded=0&downloaded=0&left=2590507008&corrupt=0&key=012FB3E6&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d8%f4%84u%afF%d2%e0%1a%f1%3f%b 5%12o%06%f9b%be!%5c&peer_id=-qB4301-.VASLJ-xefjv&port=38716&uploaded=0&downloaded=0&left=873988096&corrupt=0&key=70890948&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=6%c6td%c3z%83G%8c%ef%f5I2%b5%a9 %bd%de%a66%f3&peer_id=-qB4301-95v!5rWX4Q92&port=38716&uploaded=0&downloaded=0&left=856162304&corrupt=0&key=4C557476&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

Session 5 [Require Encryption] + [Anonymous Mode]

GET /announce?info_hash=%94%a3%15%e2%cf%80%15%b2%f65%d7 %9a%abY.m%b5W%d5%ea&peer_id=-qB4301-F8KfayWFTnBk&port=38716&uploaded=0&downloaded=0&left=2070839296&corrupt=0&key=D7CDF86C&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d1%10%1a%2b%9d%20(%11%a0%5e%8c W%c5W%a2%0b%f9t%dc%8a&peer_id=-qB4301-9OoAVgUML0ZO&port=38716&uploaded=0&downloaded=0&left=2566914048&corrupt=0&key=D3C16535&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d8%f4%84u%afF%d2%e0%1a%f1%3f%b 5%12o%06%f9b%be!%5c&peer_id=-qB4301-khSzrLGvI16Z&port=38716&uploaded=0&downloaded=0&left=846462976&corrupt=0&key=270C83A1&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=6%c6td%c3z%83G%8c%ef%f5I2%b5%a9 %bd%de%a66%f3&peer_id=-qB4301-sic5b~MygHCp&port=38716&uploaded=0&downloaded=0&left=830996480&corrupt=0&key=7F001D4E&event=started&numwant=200&compact=1&no_peer_id=1&supportcrypto=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

Session 6 [Disable Encryption] + [Anonymous Mode]

GET /announce?info_hash=%94%a3%15%e2%cf%80%15%b2%f65%d7 %9a%abY.m%b5W%d5%ea&peer_id=-qB4301-)N)5aBCwe(M3&port=38716&uploaded=0&downloaded=0&left=2064547840&corrupt=0&key=841B9502&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d1%10%1a%2b%9d%20(%11%a0%5e%8c W%c5W%a2%0b%f9t%dc%8a&peer_id=-qB4301-iGyhh)OO(qOJ&port=38716&uploaded=0&downloaded=0&left=2555379712&corrupt=0&key=981CA38A&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=%d8%f4%84u%afF%d2%e0%1a%f1%3f%b 5%12o%06%f9b%be!%5c&peer_id=-qB4301-D88kXB-rNM8f&port=38716&uploaded=0&downloaded=0&left=836501504&corrupt=0&key=4BC23B0C&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

GET /announce?info_hash=6%c6td%c3z%83G%8c%ef%f5I2%b5%a9 %bd%de%a66%f3&peer_id=-qB4301-~EuMLcNoOcxq&port=38716&uploaded=0&downloaded=0&left=825229312&corrupt=0&key=780140CB&event=started&numwant=200&compact=1&no_peer_id=1&redundant=0 HTTP/1.1
Host: ipv6.torrent.ubuntu.com
Connection: close
Accept-Encoding: gzip, deflate

What should I do if an error is found?
Report it back here the (defect) client(s) will be changed as soon as possible.

Happy Spoofing and don't get banned!:biggrin:

[anon]

Tagging this to check it later. I haven't finished checking the other stuff we spoke about yet, hoping to find time the following days.

[sashiagustina]

i am sorry to ask, anonymous mode will hide our real IP ?

[cloud99]

Hi there,
To answer your question. No. qBittorrent's Anonymous mode hides clients (qbittorrent) fingerprint from the peer-ID, sets the "User-Agent" to Null and it doesn't share your IP-address directly with trackers (though peers will still see your IP address). If you're using VPN, proxy or I2P, you probably want to enable Anonymous Mode on qBittorrent.

https://github.com/qbittorrent/qBittorrent/wiki/Anonymous-Mode
~cloud99

[anon]

i am sorry to ask, anonymous mode will hide our real IP ?



https://github.com/qbittorrent/qBittorrent/wiki/Anonymous-Mode

...and spending just a few seconds doing a search would have found that article very quickly :wsleep:

However, I don't really understand the official explanation. What is a peer_id's "fingerprint" and how is it hidden, when its prefix and structure don't change at all after enabling anonymous mode? And how is your IP not shared with the tracker when such a thing is absolutely required to receive a response? Yes, using a VPN or proxy won't share "your" IP with anything, but this feature claims to do that on its own.

To make things worse, some preliminary testing suggests that enabling it in qBittorrent 4.3.0.x doesn't even hide the User-Agent anymore! Which should be verified and confirmed for this client emulation...

[cloud99]

Before anyone comments or reports this thread as a duplicate or me for spamming the board. Please read this below: -

1) The post is a reply to the post 359161.
2) Also, the post is an answer for the Vuze/BiglyBT Extreme Mod emulation qBittorrent 4.3.0.1, not for the 4.3.0 one.



Can you confirm those?
Sorry for the delay.
Here's information on the qBittorrent version I have used.
1) I installed the 64-bit version of qBittorrent (Version 4.3.0.1). I've provided specific information regarding the setup file I've used for making the same emulation.


qbittorrent_4.3.0.1_x64_setup.exe
File Size: 24.83 MB (26032700 Bytes)
MD5 Hash: - 7edd29763454ce83f743bee6fa0fa645
SHA1 Hash: - b61ec0e3b85ec15d3ba38f5b686b1bbefb8ab922

2) I did a standard install without checking or unchecking any settings/features.
Anyway, now that we have got that out of the way. Let us move on to what I've noticed when capturing announces. Before that, here's the list of announces I captured:-


https://paste.ubuntu.com/p/7HRKwWRJv7/
https://web.archive.org/web/20201101171926/https://paste.ubuntu.com/p/7HRKwWRJv7/

I've attached an Internet archive link if the original link expires before you have a chance to go through them.
Here's what I did: -
1) I've checked the (Allow Encryption + Anonymous Mode) options and captured ten sessions with 4 announces per session, after which I've done a clean install and changed the encryption settings.
2) Next, I've checked the (Require Encryption + Anonymous Mode) options and captured ten sessions with four announces per session, after which I've done a clean install and changed the encryption settings.
3) Next, I've checked the (Disable Encryption + Anonymous Mode) options and captured ten sessions with four announces per session.
Here's what I've found with studying the announces that enabling "Anonymous Mode" in qBittorrent version 4.3.0.1 with any form of "Encryption" does hide your "User-Agent." I've restarted the client ten times (in total ten sessions) without having come across what you have with the "User-Agent" not being hidden. Also, I have done three clean installs to get the same results you have, but sadly I couldn't.

Also, I will check the second thing once I have time to do so.
~cloud99

[Renk]

Hi there,
To answer your question. No. qBittorrent's Anonymous mode (...) doesn't share your IP-address directly with trackers (though peers will still see your IP address). If you're using VPN, proxy or I2P, you probably want to enable Anonymous Mode on qBittorrent.

https://github.com/qbittorrent/qBittorrent/wiki/Anonymous-Mode
~cloud99

I was not aware of this particular point.

But something is intriguing me:
For what I understand of the torrent protocol, in case eg of seeding, first your client informs the tracker of your IP and of the list of torrent you are seeding, and then the tracker informs all peers searching for these files that you, with ip a.b.c.d on port xyz, have these. Then these peers connect to you, and the data begin to be shared (for simplicity, I don't consider PEX or DHT mechanism, supposing for example that the tracker used is a private one where these mechanisms are "usually" disabled).

But then, with "anonymous mode" enabled, how is seeding possible as you do no more inform the tracker of your mere IP???



EDIT 1:

Ok, I should have read anon's post above. :frown:

Important SBI Rule To To Remember : First read what anon has already written, and only then ask your question, if any.




EDIT 2

Things remain mysterious for me.
Here is what qbittorrent's dev exactly says now on GitHub about anonymous mode:



Anonymous Mode
Francisco Pombal edited this page 22 days ago · 8 revisions

WARNING: anonymous mode doesn't provide strong privacy guarantees on its own. If you are concerned about legal authorities and copyright trouble, for example, consider using a VPN instead (or in addition to it). Anonymous mode is only meant to further prevent your BitTorrent traffic from being associated to you, even when using other privacy enhancing mechanisms (such as a VPN service), by limiting the scope of the information broadcasted by the client (such as the fingerprint in the peer-ID).

When enabled, qBittorrent will take certain measures to try to mask its identity. The exact functionality of Anonymous Mode depends on the version of qBittorrent (specifically, libtorrent-rasterbar) being used.

If you're using VPN, proxy or I2P, you probably want to enable Anonymous Mode.

qBittorrent v3.3.0+

The peer-ID will no longer include the client's fingerprint
The user-agent will be reset to an empty string
Other identifying information will not be exposed to the public directly, such as IP, listening port, etc.

You may enable additional identity-masking features with the "Disable connections not supported by proxies" option.


qBittorrent v2.9.0 - v3.2.5

These versions of qBittorrent may make use of a version of libtorrent-rasterbar below 1.0.0. If so, enabling Anonymous Mode will enable all of the aforementioned features, plus some additional ones:

Disables Local Peer Discovery
Disables DHT
Disables UPnP & NAT-PMP
Only talks to http(s) trackers via (any) proxy
Only talks to udp trackers via SOCKS5/I2P proxy

These additional features have since been migrated to the "Disable connections not supported by proxies" option in later versions of qBittorrent.




So there is now a subtle difference with what cloud99 wrote ( "it doesn't share your IP-address directly with trackers"): Now it's "IP, listening port etc will no be exposed to the public directly" (but implicitly, the tracker is informed of them). Nevertheless this does not exhaust the question: How to share with other peers when your IP is "not exposed to the public directly" ???

[anon]

As you can see in post #5, I'm just as confused. The only confirmed effect anonymous mode has on requests is deleting the User-Agent header. The source IP is still sent at layer 3, as is the real port in the announce; trackers will reject requests where it is absent or set to 0 with failure reason "invalid port", whereas sending a fake value would work, but none of that happens.

One explanation I can think of is that it may prevent the "ipv6" (which reports your IPv6 address, if it exists, when tracker communication is done via IPv4) and/or "ip" (which is user-supplied and empty by default) parameters from being sent if they would have been otherwise. I haven't checked that because I have no IPv6 connectivity and "ip" is ignored by 99% of trackers anyway. Or maybe the documentation is outdated and doesn't apply anymore. After all, qBittorrent 3.3.0 is half a decade old, and the last edit made "22 days ago" only added the bold warning at the beginning.

[Renk]

As you can see in post #5, I'm just as confused.

I just remember something. Many years ago, you explained (https://www.sb-innovation.de/showthread.php?4279-How-To-Use-proxy-apps-for-semi-anonymous-torrenting!) how to torrent in a "semi anonymous" way. For what I understood, the trick consisted in using some free http proxy such as ultrasurf or netgate in the torrent client.

But then, the IP your client use when connecting to the tracker is the proxy's one, the tracker then gives to this IP the information abouts the peers sharing what you are looking for. But then, when an other peer connects to the tracker to get peers sharing the same torrent as you, the trackers gives your proxy IP, an ip through which no exchange is possible between peers since it is an http proxy. A side effect should be that this method limits your seed (which indeed reduces the risks). Is all that right??

[anon]

when an other peer connects to the tracker to get peers sharing the same torrent as you, the trackers gives your proxy IP, an ip through which no exchange is possible between peers since it is an http proxy. A side effect should be that this method limits your seed (which indeed reduces the risks). Is all that right??

Yes, that's correct.

However, and in hindsight, calling that "semi-anonymous" was an optimistic exaggeration. All it does is hiding your real IP from the tracker and hiding the fact you're using said tracker from local adversaries, the latter only because those particular proxy programs encrypted traffic. It doesn't conceal your location or the fact you're downloading and uploading from other peers, who also may still find you through DHT/PEX/cached peer lists. In other words, you get somewhat less exposure, but definitely not zero exposure.

On a sidenote, I was a vocal user and supporter of Ultrasurf when that thread was posted, but disavowed it after the Snowden leaks due to its status as propietary obfuscated software, reliance on United States-based proxies, bogus ownership and privacy policy, and other security issues mentioned in https://media.torproject.org/misc/2012-04-16-ultrasurf-analysis.pdf.

[sigduwksnsksis9283]

can someone upgrade this client to 4.3.3 or are we going to wait bit more?

[anon]

I for one only write these upon request. So if no one else requests or shares it, you'll be waiting forever =]

The good news is that BBTEM emulations are renamed and unobfuscated XML files in UTF-8 encoding. So if you have a copy of the documentation (which I have attached for convenience), you can create or update them yourself. The only potential caveats are the peer_id and key regeneration idiosyncrasies described at 34372, and a very weird bug that prevents the info_hash from being sent if you attempt to emulate rTorrent.

(Another fun fact: Member title users and above can also create mRatio client files with a special program available in the corresponding subforum.)

[sigduwksnsksis9283]

I for one only write these upon request. So if no one else requests or shares it, you'll be waiting forever =]

The good news is that BBTEM emulations are renamed and unobfuscated XML files in UTF-8 encoding. So if you have a copy of the documentation (which I have attached for convenience), you can create or update them yourself. The only potential caveats are the peer_id and key regeneration idiosyncrasies described at 34372, and a very weird bug that prevents the info_hash from being sent if you attempt to emulate rTorrent.

(Another fun fact: Member title users and above can also create mRatio client files with a special program available in the corresponding subforum.)
Thanks for this, maybe i will make one in few days and send it in your pm so you can check some errors..

[anon]

Note that I plan to create an "official" client file, hopefully sometime this week, since your previous post counts as a request.

Generally, qBittorrent updates only change the peer_id prefix and User-Agent string, but there have been many surprises in the past. I suggest installing the new version and capturing announces from starting and stopping different torrents, restarting the client, changing encryption settings and toggling anonymous mode, to be sure your emulation is solid.