4 ms·
> The new law sets a new standard: People should be able to use end-to-end encryption "wherever it is technically possible". In the text it is explained why thi
by fariszr 3y ago
> The new law sets a new standard: People should be able to use end-to-end encryption "wherever it is technically possible". In the text it is explained why this clear requirement to cloud providers is necessary: "Although end-to-end encryption is now the industry standard, individual messenger services do not use end-to-end encryption or only use it for certain functions, without this being justified by technical restrictions."
It's only mandatory where it's technically possible, Gmail, Instagram, Telegram and others are the ones likely to be affected.
- lxgr 3y agoI agree on Instagram and Telegram, but how on earth would you introduce E2EE to Gmail? Encrypt emails on ingress into Google? That would still not be end-to-end, though.
- bawolff 3y agoI mean, PGP and S/MIME are the two standards in this space. Both have significant deployment challenges and don't really match user needs.
- braiamp 3y agoYeah, mail not controlled by the user will still be not E2EE, since gmail needs to store it. What this could do is force mailing providers to use encryption (I do not know of a major one that doesn't)
- bennyhill 3y agoIt is technically possible to add all the support necessary to work with PGP or S/Mime encrypted emails directly in the client. I.e. protonmail implemented this.
- sigmoid10 3y agoGmail already offers E2EE for organisations since 2022. You can have your own keys and everything is locally encrypted/decrypted in the client. Google servers only see the header.
- karmakaze 3y agoTechnically it may all be possible using homomorphic encryption--it's not however practical.