Live data from Hacker News

How I encrypt my data in the cloud

robertclarke.com

61–70 of 100 posts

Re: How I encrypt my data in the cloud

#63
I recently did a small setup on my Synology consisting of a simple script that:

- Tars folders I want to backup

- Encrypts using GnuPG

- Uploads encrypted files to S3 (Glacier).

Simple and cheap cloud backup for me + nothing had to be installed on my NAS except for docker to run GnuPG and AWS CLI in containers.

Re: How I encrypt my data in the cloud

#64
post #63

I recently did a small setup on my Synology consisting of a simple script that: - Tars folders I want to backup - Encrypts using GnuPG - Uploads encrypted files to S3 (Glacier). Simple and cheap cloud backup for me + nothing had to be installed on my NAS except for docker to run GnuPG and AWS CLI in containers.

I'm not sure if it runs on Synology, but duplicity handles most of this OOTB, and handles incrementals as well.

Re: How I encrypt my data in the cloud

#67
post #55
post #43

I wouldn't trust a closed-source tool like Boxcryptor for encryption of sensitive data. Cryptomator looks interesting, though it's still a relatively new tool, and I'd be hesitant to rely on it. For my personal backups I use a combination of tar, pixz, and GnuPG. There's no fancy deduplication, and it's definitely not efficient, but it's relatively simple and I can restore individual files with ease. I run a variatio…

Isn't this basically what Duplicity does? It uses GPG to encrypt files before sending them to the remote server. https://www.nongnu.org/duplicity/

It's been a few years since I used Duplicity, and while I liked it, I prefer the Unixy one-thing-well approach of composing several smaller tools to achieve what I need.

The big thing I'm missing from Duplicity are incremental backups, which is not a strong requirement for my use case as bandwidth is cheap and I can delete the oldest N backups to free up space.

But I gain a lot from using a combination of tools: I can easily replace each component, and easily improve my workflow by adding more components, such as deduplication or incremental backups if needed.

Re: How I encrypt my data in the cloud

#68

I'd never heard of Boxcryptor. Does anyone else use this? I'm not sure I understand why I need to sign up for an account to use it if its entire purpose is to do client-side encryption. Also, it's not quite the same functionality, but this also reminds me: For a long time I've used Knox (by AgileBits, the same company that makes 1Password) for encrypted disk images, but they no longer sell or maintain it. It works ju…

You must sign up for an account to use Boxcryptor because it is paid software. That is the only reason as far as I can tell. As far as I know their servers do nothing for you once you have installed the software on your devices.

Re: How I encrypt my data in the cloud

#69

Interesting but wonder if this type of encryption ruins Dropbox business model since it keeps them from de-duping anything. I couldn't care less about Dropbox's business model... just curious.

I doubt Dropbox gains much from deduping between customers, but I'd love to see some data to the contrary. Last I knew they weren't sharing that, but most of my data is unique to me and anything I'd want to encrypt is unique to me.

I think they do gain a lot from selling 2TB to people using 30GB and selling additional users of the same <3TB of data to enterprises. (That's gotta be pretty sweet profit if they have takers - $12.50 more a month for zero additional storage and a little more data transfer.)

Re: How I encrypt my data in the cloud

#70

I think the best approach is never save unencrypted data on cloud. Always encrypted on client first. But by that way we lost dedup capability, so we have to do everything, such as encryption, dedup and compression on client side. I made an in-app file system dedicated for that purpose. https://github.com/zboxfs/zbox

> But by that way we lost dedup capability This depends on how secret do you want your data to be. You could use block-based encryption/compression and backup. That way you can still dedup encrypted result. If anyone can inject data into your system and monitor the backup, they could learn when they hit collisions, but for most personal backup cases that's irrelevant.

Dedup and encryption are 90° orthogonal. Encrypted data should look like uniform noise from every conceivable direction. Just the fact that blocks persist between encryption runs is leaking sigint.

I think a better approach, if you want to have versionable files, but encrypted outside of the client, would be to do something with diffs, similar to Git, or perhaps staged dockerfile builds, depending on whether it is binary or text data.

Post reply on HN