Hacker News Reader

Comment by gchamonlive | Hacker News Reader

If they steal your homelab, e2ee doesn't help, it's encryption at rest. E2ee is for rogue devices sniffing the network, which is more or less of a concern depending on your setup. I'd not have unencrypted traffic in my network if I had for instance those shady TV boxes.

View on HN

That’s incorrect. E2EE means encrypted data leaves the device, stored encrypted, and server(s) have no keys to decrypt it, only your (or other) client software does.

It's encryption both at rest and on transit. At rest there are levels of encryption, at object level or at filesystem level. E2ee for immich would mean the objects are encrypted and transmitting the data is encrypted. If the scenario is the server is stolen, you need encryption at rest. Even at FS level is enough.

Not sure why you're continuing to argue, GP's right.

e2ee means that the encryption keys are stored client-side by the intended recipient. It's not just in transit and in rest.

Freedom of speech

yes that does guarantee you the right to espouse stupid opinion, correct!

I've seen a lot of companies use "e2ee" to basically just mean encryption during transit, not even in rest. It's wrong, but I can see where this idea can propagate.

That’s actually true, but that’s a different issue - companies lying in their marketing materials, making claims that do not match the reality (or well-established definitions, if a company choses to mean something else and call that E2EE).

This. I think encryption is the job of the underlying operating system not the app running on top of it

e2e is not for rogue devices sniffing the network. TLS protects against that without any E2E.

TLS?

Reply on news.ycombinator.com