25 ms·
They should provide the encrypted backup to you, you decrypt it yourself. Backblaze should never see your unencrypted data.
by nailer 10y ago
They should provide the encrypted backup to you, you decrypt it yourself. Backblaze should never see your unencrypted data.
- tyingq 10y agoThey seem to be saying it's not that way because their customer base is more aligned around convenience. So it's structured where they can't see your data.... until/unless you need a restore. Is there another well known service that does this completely right? (honest ask, not a challenge) Edit: sounds like there isn't anything in their budget price range that does it well either. Sounds like it should be a goal to provide it, but hard to fault them too hard.
- throw_away 10y agohttps://www.tarsnap.com/ https://www.tarsnap.com/ It's weird that they would go through all this other effort and then have this obvious fail right at the end. Sure, I understand convenience for, say, a web UI or a mobile interface maybe, but it's really odd that they wouldn't have implemented the obvious, client-side-only version first.
- LeoPanthera 10y agoI backup to rsync.net, which is basically dumb storage. I use borg, which dedupes/compresses/encrypts, and then uploads.
- rocqua 10y agoTarsnap is a service known for being done right. It's build by the former security officer of freeBSD. It's fully aimed at power-users though. I'm sure all of my family would be more secure on backblaze because they couldn't set up tarsnap right. For myself though, I use tarsnap.
- shawkinaw 10y agoBy my math, Tarsnap is about 10x too expensive for my usage. The $5/mo I pay for Backblaze would get me 20 GB of storage on Tarsnap and no bandwidth, that's pretty poor.
- rocqua 10y agoBack when I decided, backblaze didn't work nicely with headless linux. If that changed I might consider changing. Currently I only use it to back-up the non-huge parts of my home directory and /etc. This keeps costs reasonable to me. I know these prices are pretty close to the actual cost of storage, which is amazon S3. I suppose backblaze can do better by handling their own storage.
- cookiecaper 10y agoThere are lots of options to store to most cloud backends nowadays. Check out rclone and duplicity.
- cryptarch 10y agoIt doesn't really help if you have multiple terrabytes of data, $250-$1000/month for 1-4TB is definitely a no-go for me...
- alkonaut 10y agoThat should be an option at least. I.e. "warning with this option you are responsible for the key, rather than trusting it to us with a password". I wouldn't want to be responsible for safeguarding the key to my own data if I could help it though. Or put another way: The whole reason I'm using cloud backup is because I can't be trusted with important data.
- raverbashing 10y agoYes, but this is not the service they provide If this is not sufficient, then don't use the service. It's that simple It's funny how they have to keep answering questions about this when this is not how they do stuff. They focus on easy of use. If a person is not happy with the way they do stuff then they're free to GPG stuff and upload it to wherever they think is best.
- developer2 10y agoThe reason people are taken aback by their service is that if they're going to store the private key on the server, then they shouldn't even be using client-side encryption to send the backups in the first place. It doesn't provide an additional layer of security to use asymmetric crypto the way they are using it. So why do they have it at all? To make their service sound more secure than it really is. The service is essentially using false advertising to trick nontechnical users, and that is what turns people off. You either use private keys that remain with the client, or you don't use asymmetric crypto in the first place. They're trying to mix security with convenience by eliminating the security aspect, leaving only convenience with a false sense of security.
- tyingq 10y agoSome people are taken aback. I can see their dilemma. Lots of clients are probably backing up the same PC where the key would be if they used "private keys that remain with the client". Then, they would have to deal with the blowback there when the most common scenario where a restore is needed happens. A backblaze customer's drive is dead/wiped/whatever. Right when the user needs their files back, the same drive(s) that were lost also has the private key. It seems like a reasonable solution given that constraint, and that their demographic is people wanting a cheap solution. Security isn't pushed on their front page at all really. I'd agree with your comments if they were leading with a "super secure" message. Their setup appears secure other than restoral, and you get to make the choice at that point to weigh the risk. You also have the choice of not setting a pass phrase, but encrypting your own data before upload if you want.
- 10y ago