MentalEdge

No.

I’m saying 99.999999999999999999999999999999999999999999999999999999% ≠ 100%

For some people that’s close enough. For some of us it’s not.

Prove otherwise. I dare you. I’m done putting in effort explaining the obvius to you. Your turn.

…

4

Explain to me how they couldn’t. Without simply stating “it’s encrypted”.

On the B2 plan you can use open source solutions like Kopia, and literally look at the code, to KNOW that data is encrypted on your system with keys only you have, before Backblaze ever sees it.

Explain to me, how the personal plan using their closed source application achieves the same.

Linking to a page where they say “it’s secure” is not sufficient. Elaborate. In detail. To at least an equal extent I already have.

…

Sure they can. How else do they enable providing access to the content without the user password?

The data is secured against unauthorized access, but unlike zero-knowledge setups where the chain of custody is fully within user control, the user is not the only one authorized. And even if you are supposed to be, you cannot ensure that you actually are.

OF-FUCKING-COURSE the physical drives, and network traffic are encrypted. That’s how you prevent unauthorized physical access or sniffing of data in-flight. That’s nothing special.

But encryption is not some kind of magic thing that just automatically means anyone who shouldn’t have access to the data, doesn’t.

For that to actually be the case, you need solid opsec and known chain of custody. Ways of doing things that means the data stays encrypted end-to-end.

The personal backup plan doesn’t have that.

With what?

That self hosting admins on lemmy probably care about their backups not being accessible to third parties?

I don’t think you can claim that they wouldn’t.

You can claim that YOU don’t mind. But that’s a sample size of one. And I’m not denying there are people who don’t care.

I just don’t think they’re the type to be self-hosting in the first place.

And that still doesn’t answer why the fuck you set out on this series of “well achuallys”?

It seems to me, you’re still looking for something to correct me on.

Yeah. It’s almost like I literally said that in my second comment.

Which some people are ok with, but not what most of us would want.

What gap in my knowledge are you trying to fill here?

I didn’t even mention encryption in my second comment. Just that their backup plan isn’t zero-knowledge.

No shit. But encryption isn’t the same as zero-knowledge. Where by the time they handle the data in any way whatsoever, it’s already encrypted, by you.

Do you not know what zero-knowledge means? Or are you so focused on my mentioning they’ll ship data to you physically that what I actually said went over your head?

From the page you just linked:

2. Implement encryption transparently so users don’t have to deal with it

3. Allow users to change their password without re-encrypting their data

4. In business environments, allow IT access to data without the user’s password

It’s not zero-knowledge!

Also doesn’t mean it is. Or in a way where only you can decrypt it.

The chain of custody is unclear either way. You’re not in control.

You can do that with B2. Just use an application to upload that encrypts as it uploads.

The only way to achieve the same on the backup plan (because you have to use their desktop app) is to always have your entire system encrypted and never decrypt anything while the desktop app is performing a backup.

Did you not read what I said? You use their app, which copies files from your system as-is. Ensuring it never grabs a cleartext file is not practical.

Yes. That’s not mutually exclusive with Backblaze having access to your backups.

They only needed about 500GB.

And personal is for desktop systems. You have to use Backblazes macOS/Windows desktop application, and the setup is not zero-knowledge on Backblazes part. They literally advertise being able to ship you your files on a physical device if need be.

Which some people are ok with, but not what most of us would want.

Recently helped someone get set up with backblaze B2 using Kopia, which turned out fairly affordable. It compresses and de-duplicates leading to very little storage use, and it encrypts so that Backblaze can’t read the data.

Kopia connects to it directly. To restore, you just install Kopia again and enter the same connection credentials to access the backup repository.

My personal solution is a second NAS off-site, which periodically wakes up and connects to mine via VPN, during that window Kopia is set to update my backups.

Kopia figures out what parts of the filesystem has changed very quickly, and only those changes are transferred over during each update.