Crashplan already has an option to encrypt the data. And if selected, this stores the encrypted file on the server.
Truecrypt certainly has lot more options, but for basic usage, wouldn't CrashPlan's encryption suffice?
Update: After trying CrashPlan, I'm not sure if the said encryption is anything real. Sure, it creates a container file that you cannot open and look in to, but if you go to CrashPlan's website, you can:
- see your entire folder structure
- see individual files
- restore individuals files or group of files any which way you like.
Encryption is supposed to be one-way traffic, if the data is available in plain sight, then I'm not sure if it is encryption. Maybe encoded but not encrypted. Am I missing something here?
Answer
Disclosure: I am the CEO and a Founding Partner of Code42
It's overkill. To make matters worse, it'll slow down your backups and delay data protection as the realtime monitoring wont work and encrypted data isn't compressible.
By using private data password (recommended) or generating your own key, you are ensured privacy. (Yes, you have to trust us on saying this, but unless you're a software/security expert personally studying/auditing the truecrypt code, you've got to trust something/someone.
If you have data so precious you can't trust anyone, doubling up encryption is reasonable. However, I'd only do that for that specific set of data - let CrashPlan handle the rest.
No comments:
Post a Comment