squidy/qBittorrent
1
0
Fork 0
mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-01-02 05:38:06 -06:00
Code Issues Packages Projects Releases Wiki Activity

Updated Explanation of Options in qBittorrent (mediawiki)

joopbraak
2021-09-28 16:33:08 +02:00
parent 3f44e14d72
commit d826d5146b
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
Explanation-of-Options-in-qBittorrent.mediawiki

@@ -145,8 +145,7 @@ A complete list of libtorrent configuration may be found [https://www.libtorrent
* '''Support internationalized domain name (IDN)''' — (default: disabled) When disabled, any tracker or web seed with an IDNA hostname (internationalized domain name) is ignored. This is a security precaution to avoid various unicode encoding attacks that might happen at the application level.
* '''Allow multiple connections from the same IP address''' — (default: disabled) Determines if connections from the same IP address as existing connections should be rejected or not. This option is disabled by default to prevent abusive behavior by peers. It may be useful to allow such connections in cases where simulations are run on the same machine, and all peers in a swarm have the same IP address.
* '''Validate HTTPS tracker certificates''' — (default: enabled) When set to true, the certificate of HTTPS trackers and HTTPS web seeds will be validated against the system's certificate store (as defined by OpenSSL). If the system does not have a certificate store, this option may have to be disabled in order to get trackers and web seeds to work).
* '''Server-side request forgery (SSRF) mitigation''' — (default: enabled) When enabled, tracker and web seed requests are subject to certain restrictions. An HTTP(s) tracker requests to localhost (loopback) must have the request path start with "/announce". This is the conventional bittorrent tracker request. Any other HTTP(S) tracker request to loopback will be rejected. This applies to trackers that redirect to loopback as well.
Web seeds that end up on the client's local network (i.e. in a private IP address range) may not include query string arguments. This applies to web seeds redirecting to the local network as well. Web seeds on global IPs (i.e. not local network) may not redirect to a local network address.
* '''Server-side request forgery (SSRF) mitigation''' — (default: enabled) When enabled, tracker and web seed requests are subject to certain restrictions. An HTTP(s) tracker requests to localhost (loopback) must have the request path start with "/announce". This is the conventional bittorrent tracker request. Any other HTTP(S) tracker request to loopback will be rejected. This applies to trackers that redirect to loopback as well. Web seeds that end up on the client's local network (i.e. in a private IP address range) may not include query string arguments. This applies to web seeds redirecting to the local network as well. Web seeds on global IPs (i.e. not local network) may not redirect to a local network address.
* '''Disallow connection to peers on privileged ports''' — (default: disabled) When this is true, libtorrent will not attempt to make outgoing connections to peers whose port is < 1024. This is a safety precaution to avoid being part of a DDoS attack.
* '''Upload slots behavior''' — (default: Fixed slots) It specifies which algorithm to use to determine which peers to unchoke:
** '''Fixed slots''' — The traditional choker with a fixed number of unchoke slots.