[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fn0id06IS5oq2HceV_-0vGPzZo7NHt87U5gzm1_EV0m0":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},"1a84bb52-4a30-469b-993c-b1f03d1da347","article","ECH：TLS 怎样把连接时暴露的网站域名也藏起来？","tls-encrypted-client-hello-ech","ECH 将 TLS 握手中的目标站点信息放入加密的 ClientHello，降低旁路观察者直接看到域名的机会。本文介绍 inner\u002Fouter ClientHello 的角色，并说明 IP 地址与其他元数据仍可能暴露。","访问 HTTPS 网站时，网页正文会加密，但在 TLS 握手早期，客户端通常需要告诉服务器自己要访问哪个站点。传统 TLS 的 ClientHello 中，服务器名称指示（SNI）可能以明文出现，使链路上的观察者看见域名。ECH（Encrypted Client Hello，加密客户端问候）试图把这部分早期元数据也纳入加密保护。\n\n要理解 ECH，先看 TLS 握手。客户端在建立加密会话前发送 ClientHello，里面包含协商加密参数等信息，服务器据此选择配置。为了让共享 IP 上的服务器知道应使用哪个站点配置，传统握手会携带目标主机名。ECH 采用加密的 inner ClientHello，并由外层 ClientHello 承载有限的公开信息；真正的目标站点名称放入加密部分，只有持有对应密钥的服务器端才能解开。\n\n这并不是把整个网络连接都隐形。观察者仍可能看到用户连接到哪个 IP 地址、连接发生的时间与流量大小；解析器和网络运营方也可能从 DNS 或其他信号推断访问意图。ECH 的隐私效果还受到部署方式影响：若只有少数站点启用，外层信息可能让目标范围变得明显；若多个站点共用相同入口，混淆集合更大，才更难从外部区分具体目标。\n\nECH 也需要客户端、DNS 配置与服务器端协同。客户端要获得服务器的 ECH 配置，服务器或前端基础设施要持有相应私钥并正确处理握手。网络设备、内容分发网络和网站部署方式都可能影响兼容性。某些失败场景下，客户端还需要遵循协议定义的回退处理，确保连接可靠建立。\n\n可以把它想成把目的地写进一个只有前台能打开的内层信封，再把信封交给共享前台。路上看到外层信封的人知道你去了这栋楼，却不一定知道你要找哪位住户。若这栋楼只有一家住户，隐私就弱一些；若许多站点共用同一入口，目标更难被区分。\n\n因此，ECH 不是 VPN，也不是隐藏 IP 地址的匿名工具。它针对的是 TLS 握手中可能暴露的站点名称，降低被动观察者获知具体域名的机会。用户是否能获得保护，取决于浏览器、解析服务、站点\u002FCDN 的实际支持和部署。它是隐私拼图里一块重要的补充，而非一键匿名。\n\n来源：[IETF RFC 9849：TLS Encrypted Client Hello](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9849.html)","\u002Fuploads\u002F2026-10-13\u002F598117f2-8067-4f6b-9343-3fabca289101.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},"a202d639-99a6-488a-a712-4d4c6ffd7e15","开发","dev",{"id":32,"name":33,"slug":34},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse",null,"Internet Engineering Task Force","https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9849.html","published",false,53,0,"2026-10-13T00:00:00.000Z","2026-10-13T02:13:53.346Z",[45,54,63],{"id":46,"type":6,"title":47,"slug":48,"summary":49,"coverUrl":50,"authorName":14,"sno":51,"publishedAt":52,"createdAt":53},"9ccde95c-d754-4808-91f7-488f392e3eeb","你的品牌在AI眼里到底存不存在？这套系统说了算","automated-geo-monitoring-system","靠手动抽查来验证GEO效果，本质上是在跟概率玩游戏。赢一次，不代表能一直赢。","\u002Fuploads\u002F2026-08-07\u002Fdf111c0d-f14a-4b2a-8347-141e96b71654.jpg",1,"2026-08-07T00:00:00.000Z","2026-08-07T04:31:30.843Z",{"id":55,"type":6,"title":56,"slug":57,"summary":58,"coverUrl":59,"authorName":14,"sno":60,"publishedAt":61,"createdAt":62},"9865c835-21fc-4f74-b154-19c054173557","fscrypt：只给手机里的某个文件夹加密，系统怎么做到？","linux-fscrypt-file-based-encryption","Linux fscrypt 在支持的文件系统中为目录树、文件内容和文件名提供文件级加密。它与整盘加密保护的范围不同，也不会隐藏所有文件系统元数据；本文从解锁密钥说到备份与恢复的边界。","\u002Fuploads\u002F2026-10-17\u002Fdec803fe-0da3-4a9e-8ffc-47427cf599d6.jpg",41,"2026-10-17T00:00:00.000Z","2026-10-17T03:08:37.641Z",{"id":64,"type":6,"title":65,"slug":66,"summary":67,"coverUrl":68,"authorName":14,"sno":69,"publishedAt":42,"createdAt":70},"56d3ebcb-170a-4f96-9134-ae85fb65542b","DANE\u002FTLSA：DNSSEC 能否帮助验证网站的 TLS 证书？","dane-tlsa-dnssec-tls-authentication","DANE 使用 DNS 中的 TLSA 记录发布与 TLS 服务证书或公钥相关的约束，并依赖 DNSSEC 验证记录来源。本文解释它如何补充信任路径，以及为什么它不等于所有网站都能抛弃 CA。","\u002Fuploads\u002F2026-10-13\u002F8c7d9bf5-62c6-47d4-b8eb-c4db7a21fa61.jpg",42,"2026-10-13T02:13:55.563Z"]