tbdtbd

Thanks for the tip. I do not have any Linux box around today but I have just tried with Windows7. I have two users on the same machine and I am able to create an encrypted folder on the same hard disk just by using the second user, as you suggested. It is an old machine, but I got a transfer speed of around 18 MB/s, which is reasonable even for a large amount of data. I also tried and generated the encrypted folder on a different machine, which I connected to the first one using a ethernet cable (directly between both machines). Interestingly, I got higher transfer speeds. So, it seems the bottleneck in the first experiment was the I/O of the hard disk. I also tried creating the encrypted version of the folder locally and transferring it to a remote machine, which is what I was after from the beginning. It also works perfectly well. The bittorrent sync client on the remote machine spends some time indexing the new folder and notices it does not need to download anything over the network. In summary, this "workaround" is trivial to implement on any system and gets the job done. Thanks!

Interesting. Thanks for your answer! I guess changing that part of the protocol would be a relatively big deal and it will not happen even if somebody submits a feature request, right? Out of curiosity, I had a look at the bittorrent protocol some years ago. Is the specification from October 2013 the one bittorrent sync uses? Into which fields I should be looking at in order to understand a bit better this limitation/design choice?

Yes, as a workaround I had also thought of using a virtual machine... or a container (e.g., docker), which would be a lighter solution than a VM. Nevertheless, if this was supported natively without the need to virtualize things to cheat the client, that would be really great.

Right, that is exactly what I want to do: to back up the data on my computer into an untrusted remote device. To do that, I need to first bootstrap the system. That is, I have to do the initial backup. When the amount of data to be backed up is large (e.g., several TBs), it makes no sense to do the initial backup over the network. It would take a lifetime. Instead, I would like to do it locally and copy it to the remote machine using, for example, an external USD drive. Note that this type of bootstrap functionality is supported by regular backup systems. For example, IDrive offers the IDrive Express service, which is described as follows: "Quick backup and retrieval of your data up to 3 TB in less than a week via physical storage shipment, ensuring no bandwidth usage". Having bittorrent sync support this type of offline bootstrap would be fantastic because this functionality is the only piece missing to fully support untrusted nodes. So, why is having two versions of the same folder (one with read/write rights and the other encrypted) on the same device not supported? Is this a limitation in the bittorrent protocol (e.g., the way folders and devices are identified on the wire), or is it a limitation in the client (i.e., because it checks that a given folder can exist only once)? If is is the latter one, it would be easy to fix it, I guess. Thanks!

I have a folder on my laptop and would like to back it up to a remote computer using bittorrent sync. The remote computer is untrusted and, thus, I will only install the encrypted key on it (which will give no read or write rights). This works fine when the encrypted backup is done to a remote computer over the network. However, I would like to be able to do it locally the first time because the amount of data to be backed up is large. The problem is that the bittorrent sync client does not let me create two versions of the same folder on the same computer (one with read/write rights and the other with only the encrypted key). I contacted bittorrent sync support and they answered the client simply does not support having two versions (one encrypted and one in the clear) of the same folder on the same computer. Does anyone know if there is a workaround to do that? Thanks.