How To Download Bittorrent On Linux
Amal Shelenberger
Recently I installed qBitTorrent so I could download some episodes of a Creative Commons-licensed TV series. I simply used apt-get install qbittorrent, ran qbittorrent, then added the torrent files, and pressed "start". I noticed that the series would take too long to download, so I quit qBitTorrent when it was at 10%. The next day, I launched qBitTorrent again, and was surprised to find the downloads complete. Either the 2.5 GBs downloaded within 3 seconds or something else occurred.
I have been using Qbittorrent on windows and most definitely after I quit it remains active, but there is no trace of it on the desktop except among the running processes in Win 10.I don't run it on Linux, so I don't know the difference between the two, but on Windows 10 Qbittorrent never really quits. I have to restart to make sure it's not in the background.Additionally, it doesn't seem to respond to a Force Quit either. It just sits there, consuming 0% CPU like a ghost.
Looking at the downloads page, I see that the bittorrent protocol used hasn't been updated. Why is it not updated to the new v2 protocol? It uses SHA 256 to protect against hash collisions. New torrents also run in compatibility mode, so seeding of the old version should be unaffected. It seems this should be especially important since no trackers are used and the hash is the only identifier of the torrent. Sure, it's not an issue so long as everyone verifies the signature of the image, but this seems like it would be fairly simple to change.
You're right, everyone should be verifying signatures, so authentication of the ISO file isn't the right motivation for switching. Here's a different argument without going into pgp signature validating: The bittorrent protocol is the recommended way to obtain ISO files. Since the old version of the protocol uses sha1, it is possible a bad actor could create a hash collision for one of the pieces of the torrent and seed it. Since the hashes match, torrent clients would download the piece and go on to distribute the bad piece to other peers. The whole swarm could be tainted , and many users could end up with a bad file. This is known as the BitErrant attack. To my knowledge, no one has successfully exploited this, but it is possible.
I found my WD MyPassport Wireless is running Buildroot Linaro linux with busybox; It doesn't have aptitude package manager. I don't know much about busybox; I came to know the commands provided by the busybox are called defined functions. How can I install Transmission BitTorrent client? I came across something called patch that i think provides Transmission function for the Buildroot busybox
Thank you for the clarification. Unfortunately this is a serious issue for both packages btsync and btsync-user, since in this deployment scheme BitTorrent Sync will be started using the standard linux facility start-stop-daemon that handles all the process control and PID stuff.
In conclusion I must realise that there were some serious but undocumented changes in the way BitTorrent Sync handles logging (and perhaps some more things). In order to maintain well functioning packages for linux users, I need to know, how to proceed. If you are not willing to restore the previous behaviour of logging or to make it configurable, I have to redesign fundamental parts of the init script in the btsync package and the runtime script in the btsync-user package. My only concern is: will you change this again in future?
df19127ead