I have confirmed, using dtrace, that OS X uses Intel's AES-NI instructions to accelerate encrypted disks. I found no performance decrease for batch file copies. I did not test small files nor seeking. I should run more benchmarks now that I have an SSD. Perhaps the CPU is now the bottleneck.
Depending on your threat model, they don't even have to be outside the house. If petty burglary is what you are defending against, a disk in a quiet corner of your basement is probably plenty.
I bring up threat models a lot, because I'm still fascinated with the model of data security as an adversarial relationship in which you can characterize your enemy, and thus qualify "good enough".
Being outside of the house protects it equally well against fires/floods/earthquakes/pets too. Protection against burglary is an added bonus.
It's not too hard to find one. Unless you're completely anti-social you probably have at least one tech-savvy friend that can understand the need for this kind of setup. Even better if you have more than one friend (hopefully not too be an "if") then you can have a "round robin" approach with a group of friends. An open source (so the crypto can actually be vetted) version of BTSync[1] would be great for this.
> For example, I would consider it pretty poor form to plug in a personal networked backup box at my desk at work. That kind of move can also pose a risk to my sustained employment!
Haha. Yes plugging in random networked boxes at the office might arouse some (just!) concern. When I wrote that piece I was thinking specifically of my company as I'm the boss :D
I'm most of the way through the non-Bitcoin / "Disk Space Marketplace" portion of a project that would work really well for this[1].
While the premise is that you would be able to rent disk space from anyone who wanted to provide it (using Bitcoin/Stripe/PayPal/Whatever), that part is going to be decoupled from the actual encrypt + distribute portion which could be pretty easily used by a group of friends to have reciprocal backups of important data.
I'm still a couple weekends away from it being usable though.
How DVCS was first conceived. ;)
I do use offsite backup in addition to regular local backups. I genuinely wonder how this will play out as video and image stuff to backup grows. At the least I'm thinking I probably need to do a better job of figuring out how to separate the important stuff from all the intermediate, rejected, etc. files.
There is a lot in this story that sucks but a lot that is "should have known better" as well.
It splits your data in chunks, encrypts them on the fly while sending them to the cloud. It doesn't use much space, apart from a little metadata, and you don't have to worry about the NSA, as the encryption keys are only on your local machine.
Safety deposit box at a bank, trusted non-local family member's house, and trusted international (preferably different continent) friend's house should be enough for most cases.
Regarding backups, my laptops usually rsync their /home every day to my remote server (and most data on them is in git repositories anyway).
I have over 8TB of data at my house, and getting that backed up offsite is not trivial.
Easier yet if you can pair the amount of crucial stuff to under 4TB, then it's just one drive that you can rotate monthly (weekly?).
What natural disasters/events will take out both your home and the hardened safe in your barn?
edit: An EMP may fit the bill. :-O
One of the characteristics of fireproof safes is also their ability to withstand a multi-story drop. The reason being that when the floor burns out from under it, that's what happens. This still doesn't do much to ensure data records are retained.
So long as it's a barn in the yard, reasonably directional WiFi might well suffice.
As for what natural disasters could take out your house and your barn: if you live in wildfire country, that's a distinct possible risk. As a random Google Image search example:
http://www.mesonet.ttu.edu/cases/PitchforkFire_050811/201105...
Note the plot of 20cm depth soil temperature rise (and how long the temps stay elevated):
http://www.mesonet.ttu.edu/cases/PitchforkFire_050811/meteo_...
See: http://www.theregister.co.uk/2013/12/02/setting_the_iosafe_2...
You do raise the point that fire ratings are for specific time limits: X minutes at Y temperature.
Another key point (my long-ago sources informed me) is that one of the most important things to do after the fire is to NOT OPEN THE SAFE (this applied to paper storage, inquire with your vendor / manufacturer for data).
The same properties which make a safe proof against fire damage mean that it retains heat once applied to it for a considerable period. Apparently it's not uncommon for people to employ a fireproof safe, secure their papers and documents within it, have the safe and documents survive the fire ... and then spontaneously combust when fresh oxygen is introduced on opening to the still-blazing-hot interior.
> I didn’t really trust file encryption because I thought I might lose files because of it and therefore I never enabled Mac OSX’s built-in FileVault hard drive encryption. I should have though. It’d save me from worrying about who’s going through all my files now.
This is a no brainer. I have yet to notice any real performance hit for enabling full disk encryption. Just enable it, make sure to have a long/strong password, and make sure your computer actually locks when you close the lid.
You should never be worried about losing files on a single computer. If they're important then they should be backed up to multiple computers/drives/services. If you're worried about accidentally wiping your laptop when you setup FDE then just make a backup before hand.
> My backup drive was literally NEXT to my MacBook. By sheer luck, I had just backed up my internal drive the day before and they didn’t take it.
Offsite backups are a must. It can be your own "offsite" (ie. a server at friends/parents/office) but it needs to be somewhere other than the primary site.
> I didn’t have a cloud backup because I don’t trust a third party with my data.
There's nothing wrong with not trusting third parties but that's exactly what encryption is for. Encrypt your data locally and then you can store it remotely without worrying about it being accessible to a third party. DIY scripting with GPG/S3 works well for a lot of situations. Or you can just use Tarsnap[1].
Honestly it makes a lot of sense to do the same with USB drives as well. My Linux machine is my primary computer (OS X laptop when roaming...) so the majority of my backup USB drive usage is done there. I have them setup with LUKS/dm-crypt[2] for full disk encryption. It's really easy to setup, plug-n-play on modern systems, and it almost falls into the "no reason not too" category. I just wish OS X supported it too.
[1]: http://www.tarsnap.com/
[2]: http://en.wikipedia.org/wiki/Linux_Unified_Key_Setup