安全与隐私bugzilla.mozilla.org
Bug 647959：添加“诚实的艾哈迈德”根证书
Bug 647959 – Add Honest Achmed's root certificate
2011 — 2025，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这是 Mozilla Bugzilla 上一个著名的恶搞工单：请求把“诚实的 Achmed”的根证书加入浏览器信任列表，以讽刺当时 Comodo 被入侵签发伪造证书等 CA 信任体系丑闻。帖子多年间反复登上 Hacker News，引发关于 CA 模式与信任网络（如 PGP 式信任）的讨论。
为什么经久不衰：它以幽默方式点破了“浏览器默认信任几百个 CA”这一根本性安全设计问题，至今仍是讨论 PKI 与信任模型时的经典案例。
HN 评论精选
主张用 PGP 式的分布式信任网络取代单一 CA 信任模型
问题在于我们被迫信任某个 CA，只因对方恰好从它那里买了证书。现实中，Achmed 的叔叔们信任 Achmed，可能也信任他去核实商业伙伴的身份——这正是 PGP 的逻辑。如果 SSL 能支持 PGP 式验证，任何人都可以成为根 CA，但价值取决于声誉与诚信：政府为其机构背书，朋友、企业互相担保……这样信任来源更贴近依赖方（我住在澳大利亚，Comodo 到底是谁？），还能在浏览器里以多种方式呈现这张信任网络，比如“25 个朋友和 600 家企业都认同这是 Visa 的身份”。
ra查看英文原文
The problem is that we are forced to trust a particular CA because the company we are dealing with chose to buy their certificate from that particular CA. Whilst PKI provides solutions for this [1], they are not really practical in SSL. In any case, that's not how it works in the real world. In the real world, Achmed's uncles do trust Achmed, and might well trust him to validate the identity of a business partner. In essence, that's the logic behind PGP. What if SSL could be enhanced to allow PGP verification of counterparties? That way anyone could become the equivalent of a root CA, but your value would only be as good as your reputation / integrity. Trusted entities, like the governments, could vouch for the keys of their agencies - or other governments. Friends and Family could vouch for each others keys, businesses for their partners... etc etc. Unlike PKI, PGP would enable counterparties to establish their identiy by having many validating partners (paid and unpaid), as opposed to the one single root CA that is available. As well as bringing the source of trust closer to the relying party (really, I live in Australia, who the hell is Comodo anyway?), the network of trust that would result could be articulated in the browser in many different ways. eg: 25 of your friends and 600 businesses agree that this is the identity of Visa. Twenty years ago this wouldn't have worked. But today, we could use the root CA SSL system to bootstrap a network of trust that becomes independent of the old hierarchy. I hope all that makes sense. [1] eg: certificate revocation, or even the user removing the root CA from her own key store.
指出按正规流程，只要通过审计就能成为根 CA，暗含讽刺
给好奇的人：申请成为受信任 CA 的流程见 Mozilla wiki，已收录证书及其审计报告的列表也有公开页面。只要 Achmed 先生能提供相应的审计证书……
adulau查看英文原文
For the curious, the procedure for applying to be included as a CA : https://wiki.mozilla.org/CA:How_to_apply and https://wiki.mozilla.org/CA:Recommended_Practices and the list of included certificate with their audit "certificate: http://www.mozilla.org/projects/security/certs/included/ or the pending list: http://www.mozilla.org/projects/security/certs/pending/ As long as Mr. Honest Achmed is able to provide the appropriate audit certificate...
以反讽口吻调侃 CA 犯错后总能被原谅
Achmed 是诚实的，他自己都这么说了。给他根证书吧，反正错误不会发生超过一次，而且那也只是“诚实的失误”。
pnathan查看英文原文
Achmed is honest. He even says so. Give him a root cert, certainly errors won't happen more than once, and anyway it would be an honest slip-up.
维护者现身说法：Let's Encrypt 的出现让这类问题有了实际解法
直接用 Let's Encrypt 就好。:) —— 署名：把那个工单标记为无效的人。
reedloden查看英文原文
Just use Let's Encrypt. :) Signed, The guy who marked that bug report invalid.
历次讨论
同类还值得读
非法素数
Illegal prime
维基百科条目，介绍“非法素数”：某些素数之所以被称为“非法”，是因为它们经特定编码后，恰好对应一段被法律禁止传播的数据——最著名的是 DVD 解密程序 DeCSS 的代码，有人把…
安全与隐私上首页 5 次 · 2010–2021en.wikipedia.org编辑精选关于 /dev/urandom 的常见误区
Myths about /dev/urandom
（Thomas Hühn 撰写，2014 年首发并持续更新）逐条反驳关于 /dev/urandom 的常见误解：它与 /dev/random 使用的是同一个 CSPRNG，一旦完…
安全与隐私上首页 5 次 · 2014–20202uo.de编辑精选AES 高级加密标准火柴人图解
A Stick Figure Guide to the Advanced Encryption Standard (AES)
一篇用火柴人漫画形式讲解 AES（高级加密标准）算法的经典科普文章。
安全与隐私上首页 5 次 · 2009–2022moserware.com编辑精选指纹是用户名，不是密码
Fingerprints are Usernames, not Passwords
作者（eCryptfs 维护者、Ubuntu 安全工程师）认为指纹等生物特征是公开、不可更改的标识，应视作用户名而非密码，不能当作秘密凭据用于认证。
安全与隐私上首页 4 次 · 2013–2017blog.dustinkirkland.comHTTPS 连接的最初几毫秒（2009）
The First Few Milliseconds of an HTTPS Connection (2009)
逐毫秒拆解一次 HTTPS 连接建立时发生了什么，重点讲 TLS 握手、证书验证、RSA 签名与密钥协商等机制，面向不熟悉该领域的读者。
安全与隐私上首页 4 次 · 2009–2020moserware.com编辑精选