Google unveils end-to-end messages for Gmail. Only thing is: It's not true E2EE.
Briefly

Google's recent announcement of end-to-end encryption (E2EE) for Gmail aims to provide a simplified solution for businesses and government agencies facing stringent security regulations. While the encryption happens within the user's browser, critics argue it's not true E2EE. The service replaces the cumbersome S/MIME standard, which requires complicated certificate management that results in delays and inefficiencies. In contrast, Google's E2EE allows users to encrypt messages easily—sending emails that remain secured during transmission and are only decrypted at the final destination, facilitating quicker, flexible communications without administrative headaches.
This new service allows government agencies and businesses to comply with security and privacy regulations while eliminating traditional complexities associated with deploying encrypted email systems.
Google's end-to-end encrypted messages for Gmail focus on encryption in browsers, ensuring messages aren’t decrypted until they reach the recipient's browser.
S/MIME has been notoriously complex, requiring X.509 certificates, making quick, secure communication difficult and often hindering operational flexibility.
The simplicity of Google’s approach allows users to easily activate E2EE without the needs for cumbersome certificate management, streamlining the email encryption process.
Read at Ars Technica
[
|
]