this post was submitted on 18 Jul 2026
20 points (95.5% liked)
Privacy
49906 readers
506 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Why not? It's encrypted.
It doesn't.
When you say E2EE that usually refers to encryption and decryption at each end. So the endpoints see the plaintext but it's encrypted in transit.
I think you don't want E2EE in the above sense. You want all the encryption and decryption to be on the client, i.e. you want encrypted remote storage where the server side ONLY sees ciphertext.
Anyway yeah, maybe just SSHFS or NFS to an encrypted disk image on the loopback FS of your local machine. I think the remote side shouldn't even have a file system (i.e. that exposes metadata like file sizes) rather than just a raw disk-like image. But, it could still be possible for someone monitoring disk activity on the server side to infer some things about that.
How much data are you talking about? What is your budget? You might be better off with a dedicated server, e.g. Hetzner server auction. That would make various active monitoring at the host less likely. You'd still want to encrypt in about the same way as you would a VPS.
You are trying to serve a LAN? You mention you can't use a local server, but if "can't" only means it's inconvenient, it might be worth the effort anyway. Come to think of it, a transatlantic internet connection will also be pretty slow.
If that were true, TLS/HTTPS would count as E2EE. I don't think your definition is correct, but I could of course be wrong. But yes, I want client side encryption.
But thanks, I'll think about it.
Yeah, I guess E2EE usually depicts two clients connected through a server. So the clients (the "ends") have keys but the server doesn't. In your picture there's only one "end". So it may be better to just say client-side encryption.