[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fa2RlrSAT7KZGIDg2DxLPus7k-WoQDp7zvR4MbBCWsuM":3},{"item":4,"related":44},{"id":5,"type":6,"title":7,"slug":8,"summary":9,"body":10,"coverUrl":11,"productScreenshots":12,"productLinks":13,"authorName":14,"authorUrl":15,"authorSubject":16,"category":17,"tags":22,"sourceLabel":35,"sourceName":36,"sourceUrl":37,"status":38,"seoTitle":7,"seoDescription":9,"canonicalUrl":35,"isFeatured":39,"sno":40,"sortOrder":41,"publishedAt":42,"updatedAt":43,"createdAt":43},"872963cd-242c-4912-a3dc-9497386d4772","article","Certificate Transparency：TLS 证书为什么要公开留日志？","certificate-transparency-public-audit-logs","证书透明度通过公开、可验证的日志提升 TLS 证书签发的可观察性。本文说明监控者如何发现意外证书，也厘清 CT 不会自动阻止误发。","HTTPS 网站使用 TLS 证书证明服务器身份，但证书颁发机构在签发过程中仍可能出现误发、配置错误或遭到滥用。Certificate Transparency（CT，证书透明度）提出了一个重要的审计思路：把证书相关记录放进公开、可验证的日志中，让网站运营者和监测者更容易发现意料之外的证书。\n\n可以把 CT 日志想成一份公开的签发收据簿。符合规范的日志使用追加式结构保存条目，并为日志状态提供可验证的承诺。监测者可以持续搜索某个域名相关的证书；域名所有者也能发现自己并未预期的签发记录，再联系 CA 或采取响应。公开可观察性提升了问责和发现能力。\n\n最容易混淆的一点是：CT 本身并不直接阻止证书被签发，也不会自动让浏览器判断每张证书都安全。日志记录的是可供检查的证书信息；发现异常后仍要有人监控、调查并采取措施。它与证书吊销、浏览器信任策略和 CA 审核相互关联，却不是它们的替代品。没有监测流程的日志，无法自动变成告警和应急响应。\n\n公开记录也带来隐私与治理考量。域名所有者可能不希望尚未发布的子域名过早暴露，日志生态需要维持可用性、可审计性与足够的运营独立性。不同版本的规范定义了日志接口、条目结构和证明方式；实际浏览器如何要求证书提供相关证明，也可能随策略演进。阅读资料时要区分标准的机制定义与某一时点的浏览器部署要求。\n\n对企业而言，CT 监控可以成为域名资产管理的一部分：维护域名清单，订阅或查询日志，识别未知签发，再核验是否为合法供应商、测试环境或真实误发。告警应结合组织的证书签发流程和联系人，否则容易淹没在误报里。个人用户更适合理解它作为公共审计基础设施的角色，而非把它视作浏览器上的“证书防火墙”。\n\nCT 让证书签发更可见，却不替代信任判断与响应。它体现了安全工程的一种思路：当无法保证永不出错，就让关键行为尽可能留下可验证、可被外部观察的记录。\n\n来源：[RFC 9162：Certificate Transparency Version 2.0](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9162.html)","\u002Fuploads\u002F2026-10-06\u002Fa2b8f9d0-fb90-4f19-ae2b-22cdebd395f2.jpg",[],[],"Foundit","https:\u002F\u002Ffoundit.cn","foundit-ai-editorial",{"id":18,"name":19,"slug":20,"description":21},"6179d3b6-dc34-4483-9ded-3cd9f1b37a47","科普","abbreviation","介绍各领域新兴概念",[23,27,31],{"id":24,"name":25,"slug":26},"7c76bfc2-f80f-4ee0-a95d-27bd8708b434","技术","slug",{"id":28,"name":29,"slug":30},"88d2bc27-0e0f-468a-b907-2991cb97b87b","人工智能","ai",{"id":32,"name":33,"slug":34},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse",null,"RFC 9162：Certificate Transparency Version 2.0","https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9162.html","published",false,43,0,"2026-10-06T00:00:00.000Z","2026-10-06T07:51:39.208Z",[45,54,62],{"id":46,"type":6,"title":47,"slug":48,"summary":49,"coverUrl":50,"authorName":14,"sno":51,"publishedAt":52,"createdAt":53},"3eee805c-a6c6-438b-b41c-bb67359211f6","HNSW：向量数据库怎样在“小世界图”里快速找相似项？","hnsw-approximate-nearest-neighbor-search","HNSW 把向量组织为多层可导航图，从稀疏高层逐步下探到局部候选区域，以较少距离计算近似查找邻居。本文讲解图搜索原理，以及召回率、延迟、构建和内存之间的权衡。","\u002Fuploads\u002F2026-10-13\u002Feb9f9a0c-fcbb-4323-86ea-58d5ca17c9f2.jpg",47,"2026-10-13T00:00:00.000Z","2026-10-13T02:14:06.187Z",{"id":55,"type":6,"title":56,"slug":57,"summary":58,"coverUrl":59,"authorName":14,"sno":60,"publishedAt":52,"createdAt":61},"0d29aae9-204d-474e-8eaf-e7ba96fc8064","FlashAttention：注意力计算没变，为什么显卡能少搬很多数据？","flashattention-io-aware-transformer-attention","FlashAttention 通过分块计算与在线 softmax 减少 GPU 显存往返，并避免物化完整注意力矩阵。本文解释它为何加速长序列训练，同时指出密集注意力的二次计算量并未消失。","\u002Fuploads\u002F2026-10-13\u002Faf2e6109-e447-48bf-9729-874072603e3a.jpg",50,"2026-10-13T02:14:02.226Z",{"id":63,"type":6,"title":64,"slug":65,"summary":66,"coverUrl":67,"authorName":14,"sno":60,"publishedAt":68,"createdAt":69},"f00e5274-8e0b-40fe-af3b-b6a8d0183b9c","一张贴纸就能骗过视觉 AI？对抗样本不是魔法","adversarial-examples-fool-visual-ai","人眼仍能认出的物体，经过精心设计的微小扰动或标记后，机器却可能改变判断。这类输入称为对抗样本。本文解释攻击者如何利用模型的决策边界，现实攻击为何比实验更难，以及为什么目前不存在一劳永逸的防御。","\u002Fuploads\u002F2026-09-08\u002F151f887b-c5f1-4647-b369-cdda8a1e1b4f.jpg","2026-09-03T00:00:00.000Z","2026-08-14T03:06:09.765Z"]