I've currently got BTSync dealing with a bunch of "non-private" data, and EncFS (and BoxCryptor on OS X) encrypting the more private data I'm syncing with BTSync.
I'm still "trusting" the BTSync app not to mess with my machine(s) in unexpected ways - but I have to trust every application I run to do that, Photoshop or Firefox are just as capable of "sending my data so someone else on the sly".
One thing I'm realy liking about the BTSync/EncFS setup is that I can have machines I consider "less trustworthy" to sync/store EncFS encrypted data without having EncFS/BoxCryptor installed or needing the keys. I'm happy enough for a spare machine at work, where other people might have physical access to it, to store EncFS encrypted blobs for me. I'm confident enough that's secured against pretty much everything up to federal law enforcement or nation state level snooping.
Could you please elaborate what you mean by that? As far as I know, it is not possible to "crack" EncFS or Truecrypt as long as you use reasonably strong password and are able to protect it. Or am I wrong?
It is probably good to keep in mind what you said. All passwords are only as good as your ability to keep them for yourself.
Also remember that if someone (feds) would had physical access to your computer while encrypted data is mounted, then the password doesn't matter. Even if you manage to turn off the computer, they could still decrypt the keys by "cold boot attack"[1] within minutes after shutdown. Actually anybody can do that easily. [2]
For normal-purpose encryption that this thread is about, it would be too much hassle, but if I had something I would want to really encrypt and be sure nobody would get to it, then: 1. I would use multiple layers of encryption with the possibility to decrypt one layer in multiple ways (plausible deniability) 2. Would not rely on password only, but also use some external key/token, maybe something like this: https://www.crypto-stick.com/ 3. Make the access to data quickly destroyable if I choose so. Several options come to my mind. E.g. make the key/token easily destroyable for me. Other option would be to physically destroy the media where data is stored. These would render the data inaccessible if I choose so. I would of course lose the data.
[1] https://en.wikipedia.org/wiki/Cold_boot_attack [2] http://vr-zone.com/articles/bitlocker-pgp-truecrypt-cracked-...
Of course I'd rather not have to trust either, especially with encryption. Is there an open source equivalent to BoxCryptor?
Note that EncFS "leaks" quite a bit of metadata - you might have problems explaining yourself if you've got files called blockbuster-movie.mpg or kiddie-porn.jpg - in certain configurations those filenames will be exposed (I think BoxCryptor always exposes filenames/directory-structure in the free version).
Note how the company knows how much was synced as reported in the article, although it is unclear exactly what was measured (original file sizes, data transferred, tracker statistics etc). With true privacy the BitTorrent company would have no clue what actually happened.
I wanted exactly that and built ObjectiveFS. You can try the free preview at https://objectivefs.com
But unfortunately it's not open source, so it comes down to an issue of trust--which, in the end, is the same issue with Dropbox and really the entire point of moving to self-hosted for me.
Do you trust BitTorrent to properly encrypt your data as they promise? To not send it to someone else on the sly? Etc. etc. I acknowledge the possibility of funny business is remote at best but it's one of those "on principle" things for me.
(Yes you could use another layer like Encfs or something before putting it in your BTSync/Dropbox folder but that's a pain and not really the point.)