91–94 of 94 posts
Earlier quoted context omitted.
You can actually set up app folders in Dropbox so that a particular API key effectively chroots you to that folder. The attacker would only get the backups.
Which is literally the worst scenario. An attacker owns your box and now your backups.
Earlier quoted context omitted.
Which is literally the worst scenario. An attacker owns your box and now your backups.
But if he already owns your box what prevents him from accessing your data anyway?
S3's "upload-only" API keys are a solution here: you send the backups into a black hole but the attacker can't delete them.
Looks like Dropbox might not have something like that, giving the attacker read-write access to backups if they can get that API key.
Earlier quoted context omitted.
That looks really nice, thanks. However, I've sworn off Ruby as installing and maintaining the whole Gems stack is such a pain. I'd rather write a shell script, or conjure up some Python.
Just to kid myself, I ran `sudo gem install backup` on my CentOS 7 desktop. The CPU has been pegged for over a minute, I have no idea what it's doing. It's not using much memory, and I'm not sure if it is making or hanging on network requests. EDIT: After a few minutes of warming the CPU, Ruby failed but at least with an informative error message.
Earlier quoted context omitted.
That looks really nice, thanks. However, I've sworn off Ruby as installing and maintaining the whole Gems stack is such a pain. I'd rather write a shell script, or conjure up some Python.
Just to kid myself, I ran `sudo gem install backup` on my CentOS 7 desktop. The CPU has been pegged for over a minute, I have no idea what it's doing. It's not using much memory, and I'm not sure if it is making or hanging on network requests. EDIT: After a few minutes of warming the CPU, Ruby failed but at least with an informative error message.