qBittorrent 4.1.5

[anon]

As of version 4.0.4, this client uses an individual peer_id, so it's okay to run both RatioMaster Plus and qBittorrent at the same time.

This client emulates the following settings, so make sure your real qBittorrent 4.1.5 also uses them:

Encryption mode: Prefer encryption
Listen on IPv6 address: No

[Renk]

As of version 4.0.4, this client uses an individual peer_id

Wasn't aware of that when I upgraded. When I read "individual ID" something rings in my head. Does that imply that with these new qbittorrent's versions, i am recognizable by peers from a torrent session to an other, even when changing my IP??

[anon]

For this particular client, this is how an individual peer_id works:

a different peer_id is used for each torrent you run;
it is not discarded when you stop a torrent, and the same one is used if the latter is restarted;
those values do not persist anywhere locally, so new ones are generated every time you restart the client.

So the answer to your question would be yes. Note that pre-4.0.4 versions weren't any better on that regard, as they used the same peer_id for all torrents.

There is also a "key" value that has the same idiosyncrasies listed above, but is only sent to the tracker and its function is to specifically let it identify you in the event of an IP change, so it is at least nominally desirable.

[Renk]

So the answer to your question would be yes. .
So (correct me I 'm wrong) there should be no problem if I restart qbittorrent before changing my IP ?




Note that pre-4.0.4 versions weren't any better on that regard, as they used the same peer_id for all torrents.
During all those years I have been torrenting without being aware of that.... :eek:





There is also a "key" value that has the same idiosyncrasies listed above, but is only sent to the tracker and its function is to specifically let it identify you in the event of an IP change, so it is at least nominally desirable.
So, this key changes after restarting the client correct?



PS: And what about others clients such as uTorrent (2.2.1) or BiglyBT???

[anon]

So (correct me I 'm wrong) there should be no problem if I restart qbittorrent before changing my IP ?

Correct.


During all those years I have been torrenting without being aware of that.... :eek:

Don't worry, this risk is more potential than real. Copyright trolls are more interested on finding that you downloaded anything at all rather than building long-term activity profiles, not to mention most clients use random identifiers nowadays (see below), which would make the practice less practical anyway.


So, this key changes after restarting the client correct?

Correct.


PS: And what about others clients such as uTorrent (2.2.1) or BiglyBT???

uTorrent 2.2.1 generates a single peer_id and key on startup and uses it for all torrents. Versions 3.3 build 27841 and above improved this to generating a random peer_id for each non-private torrent unless explicitly disabled.

BiglyBT uses an individual peer_id and key for each torrent, and regenerates them whenever you stop and restart it (the torrent).

For other clients, see http://www.sb-innovation.de/forumdisplay.php?275-Client-File-Knowledge-Base

[Lucius]

random peer_id for each non-private torrent unless explicitly disabled

So this random generating thing is just for public torrents not the torrents with the private flag? Nice info, seems I didn't dig enough.

[anon]

That's right, they knew anti-cheating scripts that expect the usual behavior would go crazy otherwise :happy:

However, it should still be turned off, so that the memory readers in mRatio and RM+ don't pick up a random peer_id from a public torrent if you have one running.

[Lucius]

However, it should still be turned off, so that the memory readers in mRatio and RM+ don't pick up a random peer_id from a public torrent if you have one running.

You don't need to if you use the remote memory reader ;)

[anon]

You don't need to if you use the remote memory reader ;)

I try to cover all possible usage scenarios :gredface:

[Lucius]

Oh, The dummy torrent has no private flag. (Note taken)

[anon]

Oh, The dummy torrent has no private flag. (Note taken)

It doesn't? I just generated a dummy torrent in RM+ 2.1.0 and the private flag is there =]

[Lucius]

It doesn't? I just generated a dummy torrent in RM+ 2.1.0 and the private flag is there =]

Long time no coding, thanks for the heads up.