If you have a set of files that you wish to share with someone, but don't want to use cloud storage services, there are a few options that you can use. Syncthing or Resilio Sync come to mind, or traditional options such as FTP.
But there is a simpler way: creating a private torrent. All you need is a BitTorrent client and a couple of minutes to set it up correctly so that your files can be shared to as many users as you like.
Let's get started. We are going to assume that you know how to open a port on your router to configure port forwarding. Usually this involves accessing the router page in your web browser and selecting a port that you wish to forward. It varies for most models; refer to your router manual or the OEM's website for instructions.
Tip: use the port forwarding tester to test if a port is forwarded properly.
For e.g. qBitTorrent by default uses port 9000 for the embedded tracker. So if I were to open a port on my ZTE F612W router, I'd navigate to the following path in the router's page: Application > Port Forwarding and set the port that I want to.
If you don't use the embedded tracker and private torrent options, the torrent that you create will be public, i.e., it will be visible to all and anyone may (in theory) download the files.
Your torrent should start seeding immediately if you did it right. You can also verify this by navigating to the tracker tab, the status should say "working".
Remember the torrent file that was saved when you created the torrent? Send that to the people that you want to share the files with. If the files are important, use encryption or secure messaging options.
Is this secure? It depends on how the torrent file is shared and what kind of files you are sharing. Note that your network operator / ISP may still see what you are sharing and seeding.
This can be a great way to share tons of Gigabytes worth of content without having to upload them to cloud storage services.
I wrote this guide to simplify and explain the steps found in the official qBittorrent Wiki article.
Please click on the following link to open the newsletter signup page: Ghacks Newsletter Sign up
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.
This looks like a horribly complicated way of sending bulky data to a single person, and bittorrent isn’t even really intended for that (a single recipient). But it’s true that surprisingly, there isn’t a good standard solution to this problem in 2019 (relevant xkcd: https://xkcd.com/949/). My suggestion would be client side encrypted file sending services like instances of Lufi, or instances of Up1, or Firefox Send.
I always find this certain xkcd picture interesting, because I agree with that until that “early adopters” part. Because sharing files is still surprisingly complicated these days, either due to size limits, speed limits, availability limits, etc. To directly share a file privately and peer to peer, I found that file.pizza (source code available) works incredibly well. There don’t seem to many alternatives that are this fool-proof and easy to use.
Onionshare is a new thing. Haven’t tested it personally but others have vouched for it.
IDK, but I imagine this is a good option if you are on Linux or BSD?
In Windows, there are other free options which I like better, such as with FileZilla + Duck DNS.. that is when you want “to share tons of Gigabytes worth of content”.
As for for basic cloud sharing of a few files for free, WeTransfer is hard to beat, as it’s fast, simple, and no crazy ads.
Thank you, very useful
This really helped me out. Thank you!
The “Enable embedded tracker” box was not ticked when I installed the program.
Thanks this saved me some time. That box isn’t checked by default and it makes the torrent fail to “not working” status
>Is this secure? It depends on how the torrent file is shared and what kind of files you are sharing. Note that your network operator / ISP may still see what you are sharing and seeding.
How? The traffic will be encrypted, so how would they possibly see anything beyond encrypted data with no other identifying metadata?