3 ms·
I took this to mean that since the user side has full access to the plain text, the user client could calculate a delta, then encrypt it and upload just the enc
by ColinDabritz 14y ago
I took this to mean that since the user side has full access to the plain text, the user client could calculate a delta, then encrypt it and upload just the encrypted delta.
You'd still need to pull it all down and apply the deltas each time you put it somewhere new, but it would work. Possibly with a 'full version' on some longer schedule. As a bonus, you'd get automatic history, which Dropbox stores anyway.
It's still got issues, no doubt, but it could be done, no?
- keeperofdakeys 14y agoWhat you describe is nearly exactly how an encrypted backup service called tarsnap works. Basically, it provides de-duplicated, compressed backups to the Amazon S3 cloud using local key files. The difference here is that it deals with data in blocks, not explicit deltas. This means you have no concept of 'history', and separate archives on the service have no strict dependencies on each other (they merely reference certain blocks that have been uploaded). It uses a cli-only interface inspired from tar, and is very handy for cron backups of important data. There is also a project called ddar, which is designed to provide merely the de-duplication of tarsnap so you can setup your own repository (tarsnap only works with its service).