Re:RCE Vulnerability in QBittorrent
by fulafel on Saturday November 02, 2024 @12:55AM
(#42024156)
What's considered the most secure Bittorrent app?
[ Parent
| on HN ]
qBittorrent after the most recent update...
Re:RCE Vulnerability in QBittorrent
by johnisgood on Saturday November 02, 2024 @09:47AM
(#42026368)
Why not Transmission?
transmission is great if you're just getting linux images, but it's much easier to configure qbittorrent for stuff like VPN lockout and such
Re:RCE Vulnerability in QBittorrent
by ndsipa_pomu on Saturday November 02, 2024 @12:42PM
(#42027452)
It's pretty easy to combine docker containers for torrenting and a VPN so that the torrenting doesn't get any network access until the VPN successfully connects. However, I use qbittorrent myself (containerised of course).
Re:RCE Vulnerability in QBittorrent
by johnisgood on Saturday November 02, 2024 @06:48PM
(#42029791)
Why for Linux images only? I use it with everything. You do not even need to use the GUI, there is transmission-cli. There is transmission-daemon as well, controlled by transmission-remote (or Transmission's web interface), meaning that you can use it on a seedbox.
The one in a restricted container.
Re:RCE Vulnerability in QBittorrent
by steelframe on Saturday November 02, 2024 @08:44AM
(#42026075)
This is exactly what I do with any software that talks to the Internet. However I'd still really, really like for an advanced adversary to not have arbitrary RCE on my machine, whether it's in a container or not. Any zero days in my kernel that said adversary may have in their back pocket are then exposed for exploitation.
Containers aren't strong security boundaries so the question still remains. If you get RCE in a containerized app you can tickle eg host kernel bugs, container runtime bugs, etc.
Without a formal audit on a variety of BT clients, this isn't really an answerable question. Just because this one issue was discovered in qBT, doesn't mean that there are hundreds more in it, and Transmission, say, has none.