ProdigySim

Thanks for the information, as well as your suggestion. I will probably use some sort of client-side encryption along the same lines. The encfs --reverse sounds like a good solution for a one-way backup, but I'm curious as to how it will handle the "Sync" scenario--where changes may originate from an external node and must be replicated on the local (encrypted) filesystem.

Hey, I'm interested in trying to develop some sort of rudimentary encrypted backup system for myself using BT Sync. I'd like to host a Sync node for myself in the cloud--someplace where I can have better uptime, stability, and data redundancy than on any of my few client nodes. But, being security-minded, I don't see any reason to allow this node to decrypt my data. Is there any way I can use BT Sync to create such a non-decrypting node? If not, is decryption necessary to perform properly as a node in a BT Sync network? i.e. do I have to trust all of my nodes in order to use BT Sync?