4 ms·
When I first set up my Drive account it wasn't the U.S. government I was worried about, it was Google itself. That's why I put all of the files I wanted to sync
by cliveowen 13y ago
When I first set up my Drive account it wasn't the U.S. government I was worried about, it was Google itself. That's why I put all of the files I wanted to sync in an encrypted image (which you can create with Disk Utility on Mac OS X) and then uploaded the image. Also, to avoid re-uploading the whole shebang (which is more than a GB) I use a sparse bundle disk image which means that if I modify a single file only a small portion of the image will be re-synced with Drive.
- toomuchtodo 13y agoI do the same thing, but with Truecrypt and Dropbox.
- guiambros 13y agoHmm, does sparse bundle work well with TrueCrypt? Any consistency issues when sync'ing with Dropbox?
- toomuchtodo 13y agoI didn't use a sparse bundle, just a TrueCrypt container. It uses the full space allocated on disk, and I've rarely had an issue (1-2 times over 4 months) with Dropbox syncing.
- guiambros 13y agoThanks. I research more, and seems that TrueCrypt still does not support sparse bundle, so that's still a no go. The only option is to do what you did, sharing a full container. But if you have a big container (say, 1GB or so), it has the drawback of re-syncing the file back-and-forth. And if you have multiple devices (including mobile, etc), this would easily became a nightmare. That's a bummer. I love TrueCrypt for local encryption of filesystems and containers, but I wish I could use as a lightweight, on-the-fly, encryption of files. Particularly dropbox and other cloud-based storage.
- hannibal5 13y agoGood idea. Sparse bundle gets around the fact that Google don't use block level delta sync with drive yet. I use trucrypt + dropbox combination because DropBox has delta sync, but your way makes Drive also a good option.