Gmail 的端到端加密功能和预期一样糟糕。
Gmail E2E is as terrible as expected

原始链接: https://michal.sapka.pl/2025/gmail-e2e-is-as-terrible-as-expected/

谷歌于2025年4月6日宣布的Gmail“端到端”加密,实为虚晃一枪,并非真正的端到端加密。它并没有采用标准的密钥交换,而是强制收件人使用“简化版Gmail”界面来解密邮件,即使没有谷歌账户也一样。这意味着阅读经过Gmail加密的邮件需要使用谷歌的服务、浏览器,并忍受谷歌的追踪。 这种做法赋予谷歌过度的控制权。IT团队可以强制外部收件人使用受限的简化版Gmail,本质上将邮件视为谷歌文档,可以随时撤销访问权限,使谷歌成为邮件的实际拥有者。用户无法在未经谷歌许可的情况下阅读、搜索或管理自己的邮件。实质上,邮件变成了谷歌控制的单纯通知渠道,发件人不得不立即将其添加到垃圾邮件过滤器中。

Hacker News 上的一篇讨论批评了 Gmail 端到端加密的实现方式,认为它复制了安全电子邮件中已存在的问题:将电子邮件变成指向安全门户网站的通知链接。评论者指出,这种方法在医疗保健(HIPAA 合规)和银行等行业很常见,因为普通用户对真正安全电子邮件(如 PGP)的采用率很低。密钥管理的复杂性是一个障碍,导致人们依赖于集中式、通常是特定国家的安全门户网站。一位评论者对客户端 JavaScript 处理加密内容的安全风险表示担忧,尤其是在 ProtonMail 和 MEGA 等服务中,因为信任 Google 处理客户端页面就违背了端到端加密的初衷。普遍缺乏用于验证签名资产和确保代码可信的浏览器扩展程序仍然是一个重要的未解决问题。总体而言,人们认为确保电子邮件安全仍然是一个挑战,需要合作、切实可行的规章制度以及摆脱专有的“护城河”式解决方案。
相关文章

原文

Google announced that end-to-end encryption would be coming to Gmail. What a sweet day! Finally Google does something good. Is it a new protocol to exchange public keys? Maybe some way to fetch public key from destination server? Oh sweet summer child.

The way Big G did it, is in the most annoying way. The sender encrypts the message with her own key, an email with link is sent to receiver and if he wants to read it, he needs to open something they call "minimal gmail". Yes, you've got that right. To read an email sent from Gmail, one needs to use Gmail, even he never had any Google account.

I'm not going into how much this is not E2E, as this has already been proven. But what I annoyed me the most is how Google assumes that only Gmail is worthy to read email from Gmail.

Until recently, there were basically three subcategories of email:

  • Normal email
  • Gmail
  • Outlook

While the underlying exchange protocol is standardized,the later two have enough big market share to add custom behavior. And no one cared, because if you're using G or O, you have no one else to blame but yourself (or your employee). All we care about is being able to send email to the big two, which can be pain in the ass (I've heard).

But this power move is different. If I receive an "e2e" encrypted email from gmail, I will not be able to read it without going to a Google service. This means browser, javascript, tracking and all that crap.

"IT teams also have the option to require all external recipients (even if they are Gmail users) to use the restricted version of Gmail. This helps ensure that their organization’s data does not end up stored on third-party servers and devices. It also makes it easier for organizations to protect their data by having the ability to apply security policies and revoke access to emails, no matter how long ago they were sent. Essentially, the E2EE email becomes like a document in Google Drive, allowing the IT team to control its access."
-- Google's documentation

This makes Google the actual owner of the sent message. I can not read it (I will not open gmail!), I can not search for the email, I can not do anything. My Email becomes just a notification channel I pay for. "The recipient can then use a guest Google Workspace account to securely view and reply to the email" my ass.

Ergo: such emails go directly into spam list.

联系我们 contact @ memedata.com