Added content based on comment
This commit is contained in:
parent
b09c5dd6c9
commit
01a80468e6
BIN
opsec/syncthing/Syncthing_circuit.jpg
Normal file
BIN
opsec/syncthing/Syncthing_circuit.jpg
Normal file
Binary file not shown.
After Width: | Height: | Size: 24 KiB |
@ -61,8 +61,8 @@
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<a href="../index.html">Previous Page</a></br></br><p><img src="../../assets/img/user.png" width="50px" height="50px"> <ba>Prism_Breaker</ba></p>
|
||||
<h1>Use syncthing to share big file over tor </h1>
|
||||
<p>Onionshare is a good choice when you want to share small files over tor. But onionshare cannot handle big files, when tor circuit fails(which is quite common) your download simply fails, and it does not support resuming the download at where it fails. Syncthing is a better alternative for sharing big files over tor, because it will automatically retry at break point when network fails.</p>
|
||||
<h1>Use syncthing to share large file over tor </h1>
|
||||
<p>Onionshare is a good choice when you want to share small files over tor. But onionshare cannot handle big files, when tor circuit fails(which is quite common) your download simply fails, and it does not support resuming the download at where it fails. Syncthing is a better alternative for sharing big files over tor, it does not need any setup or hosting, and it will automatically retry at break point when network fails.</p>
|
||||
|
||||
<p>Syncthing is FOSS software and has E2EE by default, and can run without a clearnet ip address. This means you can just spin up a client, and your data will be encrypted and sent through syncthing network. If you have a threat model that needs a way to reliably share files with minimum exposure, this setup will be suitable.</p>
|
||||
|
||||
@ -93,8 +93,11 @@ It is highly recommended to use whonix for this setup, because there are always
|
||||
<div class="row">
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>Initial Setup </b></h2>
|
||||
<p>The first thing to do is to get syncthing to your whonix workstation. Download the syncthing client from their website</p>
|
||||
|
||||
<p>The first thing to do is to get syncthing to your whonix workstation.</p>
|
||||
<p>For simplicity you can just do</p>
|
||||
<pre><code class="nim">sudo apt-get install syncthing
|
||||
</code></pre>
|
||||
<p>Sometimes apt might not contains the up to date package, then you need to get it from the site</p>
|
||||
<img src="1.png" class="imgRz">
|
||||
|
||||
<p>Next verify the sha256sum according to <a href="https://syncthing.net/security/">https://syncthing.net/security/</a></p>
|
||||
@ -140,6 +143,7 @@ sha256sum: WARNING: 35 listed files could not be read
|
||||
<img src="2.png" class="imgRz">
|
||||
<p>serach for no_proxies_on in the search bar, and add 127.0.0.1 to it</p>
|
||||
<img src="3.png" class="imgRz">
|
||||
<p>Editing your tor browser is fine if you are just using it to access local syncthing instance, but you should revert the change if you want to access the internet. Changing tor config might bring some unexpected browser fingerprint issue. You should get a separate whonix vm if paranoid.</p>
|
||||
|
||||
|
||||
</div>
|
||||
@ -188,17 +192,23 @@ $ ./syncthing
|
||||
<div class="col-lg-8 col-lg-offset-2">
|
||||
<h2><b>Sync files</b></h2> </br> </br>
|
||||
<p>After the previous setup, you can share the file you want</p>
|
||||
<p>Syncthing over tor is really slow! Because if both parties are behind tor, your file will probably goes through a circuit like this: </p>
|
||||
<img src="Syncthing_circuit.jpg" class="imgRz">
|
||||
<p>I personally tried this setup, and it took me 4 hours 30 minutes to send a 10GB file. So be patient when you are sending some large files</p>
|
||||
|
||||
<p>You and your peer will only see the relay server's ip address, unlike the vpn setup which will expose the vpn ip you are using, which you can check here <a href="https://blog.nowhere.moe/opsec/syncthingvpn/index.html">https://blog.nowhere.moe/opsec/syncthingvpn/index.html</a></p>
|
||||
<p>You peer also won't know you are using tor if you do not tell him</p>
|
||||
<img src="remote_node.png" class="imgRz">
|
||||
|
||||
|
||||
<p>Choose add folder to create a new sharing Folder, and choose to share this folder with your peer</p>
|
||||
<img src="9.png" class="imgRz">
|
||||
<p></p>
|
||||
<img src="10.png" class="imgRz">
|
||||
|
||||
<p>If nothing goes wrong, the receiver should this</p>
|
||||
<p>If nothing goes wrong, the receiver should see this</p>
|
||||
<img src="11.png" class="imgRz">
|
||||
<p>Agree and add the folder, after that syncthing will automatically transmit the files</p>
|
||||
<p>The last remainder is syncthing over tor is really slow! Because if both parties are behind, your file will probably goes through a circuit like this: You -> Yours three tor nodes -> Syncthing node -> Receiver's three tor nodes -> Receiver</p>
|
||||
<p>I personally tried this setup, and it took me 4 hours 30 minutes to send a 10GB file. So be patient when you are sending some large files</p>
|
||||
|
||||
|
||||
</div>
|
||||
</div><!-- /row -->
|
||||
|
BIN
opsec/syncthing/remote_node.png
Normal file
BIN
opsec/syncthing/remote_node.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 24 KiB |
Loading…
Reference in New Issue
Block a user