Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - chrstphrchvz

Pages: [1]
1
MAC / Re: [UNOFFICIAL] qBittorrent 4.1.4 for macOS
« on: February 11, 2019, 02:47:32 AM »
I'm running Mac Mojave and qBittorrent 4.1.5 and I don't see an option for Dark Mode. Where do I find this?

Do you mean the official 4.1.5 build? Right now that uses a slightly older version of Qt (5.9.7) which does not support dark mode. A more recent version such as Qt 5.12 is needed for dark mode support. See https://github.com/qbittorrent/qBittorrent/issues/9096#issuecomment-450740412 for a newer build that supports dark mode.

Also, there won't be an "option" that appears in qBittorrent preferences to use dark mode; rather, qBittorrent will automatically follow whether or not dark mode is set in System Preferences.

2
MAC / Re: Help with pausing seeding
« on: November 20, 2018, 09:28:59 AM »
Pausing a finished torrent will stop it from seeding. Then, when you want to seed it, just un-pause it. Maybe also play around with the upload rate limit to see what works for you.

You might check out the feature in Preferences > Speed > "Alternative rate limits" > "Schedule the use of alternative rate limits". If there is a certain time of day you will or won't be using your computer, then you can use that to increase or reduce the upload rate limit during a set time. To my knowledge there isn't something included in qBittorrent to automatically do this when your computer has been in use during the past x minutes.

If you have already downloaded a file and still have the corresponding .torrent file for it as well, then just open the .torrent file in qBittorrent and making sure the "Save at" path is where the already-downloaded file is. When the torrent is started, qBittorrent will recheck the file's integrity and begin seeding it.

(I don't make the rules for file-sharing sites, but I don't think it's realistic to expect torrent users to seed everything they've downloaded 24/7; not everyone has that luxury. Seeding only when convenient can still go a long ways. If you're concerned about this though, the key thing to watch is your ratio or "reputation" as measured by these sites' trackers.)

3
You have DHT enabled (Preferences > BitTorrent > Privacy > "Enable DHT (decentralized network) to find more peers"). It will connect to those sites because they are "DHT bootstrap nodes".

Searching qBittorrent's source code, these are indeed hard-coded into qBittorrent:

https://github.com/qbittorrent/qBittorrent/blob/2ce57b97be4483c9f532231a9dd7b5e6cd6a8242/src/base/bittorrent/session.cpp#L1418
https://github.com/qbittorrent/qBittorrent/blob/2ce57b97be4483c9f532231a9dd7b5e6cd6a8242/src/base/bittorrent/session.cpp#L1696

This isn't a Mac-specific or even qBittorrent-specific behavior. The same bootstrap nodes can be found hard-coded into other open source DHT-supporting BitTorrent clients as well.

4
MAC / Re: Unable to 'gpg --verify' the installation file.
« on: November 19, 2018, 01:18:48 PM »
Where is the qbittorrent-4.1.3.dmg file you downloaded? If you don't specify where it is, and it's not in the same directory as the .asc signature file, then you will get the error:
Code: [Select]
$ gpg --verify qbittorrent-4.1.3.dmg.asc
gpg: no signed data
gpg: can't hash datafile: No data

If both the .asc and .dmg were in the same directory, then your command would have worked:
Code: [Select]
$ gpg --verify qbittorrent-4.1.3.dmg.asc
gpg: assuming signed data in 'qbittorrent-4.1.3.dmg'
gpg: Signature made Tue Sep 18 17:33:37 2018 CDT
gpg:                using RSA key D8F3DA77AAC6741053599C136E4A2D025B7CC9A2
gpg: Good signature from "sledgehammer_999 (Used for signing git commits/tags/etc) <[email protected]>" [unknown]
gpg:                 aka "sledgehammer999 (Used for signing qBittorrent source tarballs and binaries v2.) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: D8F3 DA77 AAC6 7410 5359  9C13 6E4A 2D02 5B7C C9A2

Notice that first line: assuming signed data in 'qbittorrent-4.1.3.dmg'. If it's not in the same directory, then you must specify exactly where you downloaded the qbittorrent dmg file to, i.e. gpg --verify some/path/foo/qbittorrent-4.1.3.dmg.asc some/path/bar/qbittorrent-4.1.3.dmg

This is all described in man gpg.

5
Hello, fellows!

Could someone please clarify if the solution decribed above presents any threat to privacy of my machine? What's the catch? If it's so easy to fix - why it was never fixed in app itself?

Please refer to the original thread this one was split from for more background. The qBittorrent team decided 3 years ago that they will not perform any fixes or workarounds themselves, as they blame the issue entirely on macOS' firewall for it not dealing with unsigned programs like qBittorrent correctly.

(However, given the trend of major operating systems moving toward mandatory code signing, I don't think Apple will ever address whether macOS' firewall works with unsigned programs or not.)

Signing qBittorrent doesn't change the program itself; think of it as a way of letting macOS know "this program hasn't been tampered with", which in this case happens to get around the "bug" in macOS' firewall. As this workaround only helps ensure normal operation of qBittorrent, it poses no increased risk to privacy than when using qBittorrent normally.

6
Original thread poster here.

Thanks for finding this, it's the same as the workaround that @chriswayg identified on Github issue #3885, and @madranet says it indeed does not survive updates.

However, I am under the impression no qBittorrent-side fixes would be considered as the consensus is that the issue due to a "firewall bug".

7
Suggestions / Pause downloading/seeding while on battery
« on: August 18, 2016, 08:48:50 PM »
Detect when the system is running off of battery power, and allow the user able to configure whether or not seeding and/or downloading should be allowed while on battery.

I don't know what load is typically needed before qBittorrent starts using up significant energy, but I imagine it could still help conserve energy while on battery (or give a server more runtime if running on UPS).

I have not done any programming related to battery events, so I might not be able to implement this myself anytime soon. I understand implementing such a feature may vary considerably between platforms.

8
I think the problem lies somewhere in a fact, that qBittorrent binary does not call to open/listen/etc. connections, instead it is done by other binary/library. This somehow confuses Mac's Firewall.
Is that the case?
Does qBittorrent binary consits of qBittorrent object and  Libtorrent object, or is Libtorrent a dynamic library? Same question applies to Libtorrent's dependencies.

I don't know how dumbed down is the OSX GUI, but on Windows the firewalls have an advanced view/info pane that will always point to the exact binary and to the exact path, to the network interface, the incoming/outgoing ip, port etc.

Does OSX have something similar? If yes, does the binary pathc/name stay the same between runs? What about the incoming port? Are the firewall rules that get created correct?

In the client version of OS X, the user-friendly "application" firewall is strictly by system sharing services (e.g. SMB, VNC) and .app files or other identified binary files, and there are two options: allow and block, and only for incoming connections. I assume that when allowed, it is on all ports possible, since it is not configurable here. There are other separate BSD firewall services included (ipfw, pfctl) but, lacking a GUI frontend in the client version of OS X, they would not be responsible for the recurring prompt, and neither of which have I modified their default configuration nor are familiar with their operation.

As for the theory that OS X records an exception for the wrong "aspect" of qBittorent, it seems to go against the idea of how the application firewall is supposed to behave in this case, since qBittorrent is installed here as a standalone "bundle" like some other ordinary apps on OS X. The Activity Monitor app typically shows if a "helper" process is responsible for generating network traffic, and in this case only qBittorrent.app is listed. Digging into the .app file, the application firewall does allow specifying individual binaries and .dylib files; I do not know if it is the case that only the main MacOS/qbittorrent binary is allowed, but I would assume that so are the frameworks and dynamic libraries.

Nonetheless, given just the symptoms of the issue, the application firewall could be at fault, and not qBittorrent.

9
MAC / Re: qBittorrent 3.2.0 git compiles thread
« on: June 23, 2014, 02:22:00 AM »
This has been going for couple versions now, also in this version too: every time I start qBittorrent it asks me to Allow/Deny incoming network connections.
I've clicked Allow, and even explicitly deleted qBitorrent and added it again in Firewall, but it still keeps asking me every time. I don't want to disable this security feature, but it would be also nice if qBittorrent would start without asking me this every time.
Any ideas how to fix this?

P.S.
I have some thoughts, that qBittorrent is doing something unusual, because similar applications work fine.

ignas2526, I have opened a topic just for that issue, could you add any details over there?
http://qbforums.shiki.hu/index.php/topic,2644.0.html
Thanks!

10
Here is a screenshot of the connection settings. I suspected the "use different port" myself and sure enough it was already unchecked. Any other settings to check though?

11
MAC / "Accept incoming connections" every time qBittorent is opened
« on: June 22, 2014, 05:36:35 AM »
[EDIT: a workaround has been stickied as well as an issue on GitHub opened.]

Hi,
I am running OS X 10.9.3. I am using littletree76's builds, and, at least for the recent versions (3.1.9.1 to 3.2.0 alpha) every time qBittorrent is opened, I get the "Deny/Allow incoming connections" prompt from the Firewall, even though I have clicked "Allow" the previous time the program was opened, and qBittorent is listed as "Allowed" in System Preferences (see the attached screenshots).
Is anyone else experiencing this? I find reports for other programs doing this (mainly Java-based ones) going back several years, but haven't found anything that would apply to qBittorent.

Pages: [1]