[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGZ0mbz9joZobHPsYx8ql8Cne4ht8A7KVkP-_gxFWF3o":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":35,"sourceUrl":36,"status":37,"seoTitle":7,"seoDescription":9,"canonicalUrl":38,"isFeatured":39,"sno":40,"sortOrder":41,"publishedAt":42,"updatedAt":43,"createdAt":43},"36d176d2-1106-420a-99d5-543df1e9e22f","article","ML-KEM：后量子密码里的“密钥封装”到底封装了什么？","nist-ml-kem-post-quantum-key-encapsulation","ML-KEM 是 NIST 标准化的后量子密钥封装机制，通信双方借助它得到同一份共享密钥，再用对称密码保护实际数据。本文解释封装与加密的区别，以及“后量子”是面向威胁模型的设计目标，不是永不失效的承诺。","“量子计算机会不会破解今天的公钥密码？”这个问题促使密码学界研究后量子密码。NIST 标准化的 ML-KEM（Module-Lattice-Based Key-Encapsulation Mechanism）是其中一种密钥封装机制。名字里有“封装”，容易让人以为它直接加密整段聊天或文件，其实它主要帮助双方建立共享密钥。\n\n## 先协商钥匙，再加密真正的数据\n\n接收方先生成一对密钥并公开公钥。发送方运行封装过程，得到两样东西：一段可以传给接收方的密文，以及一份共享秘密。接收方用私钥解封装同一份秘密。双方随后将共享秘密交给密钥派生与对称加密算法，用来保护实际通信内容。\n\n可以把它比喻成一台无人值守的取钥机：公开信息足以让任何人投递一个包裹，并与接收方计算出同一把临时钥匙；只有持有私钥的人才能从包裹中恢复那把钥匙。实际货物仍需要另一把高效的锁来保护。这个分工解释了 KEM 与传统“公钥直接加密文件”之间的差异。\n\nML-KEM 基于模格问题构造，目标是在已知量子算法威胁模型下提供密钥建立能力。NIST FIPS 203 将其标准化，并定义不同参数集供系统按安全与性能需求选择。后量子表示设计目标考虑了未来量子计算风险，不等于数学上永久不会被攻破，也不代表部署后无需更新。\n\n## 密码迁移是系统工程\n\n应用能否使用 ML-KEM，不只取决于调用一个库。协议要定义如何协商算法、如何编码封装消息、如何处理失败，以及如何与证书、会话密钥和身份认证配合。现有设备、TLS 库、网络中间件和硬件加速能力也可能影响兼容性与性能。\n\n在迁移期间，有些系统会研究传统算法与后量子算法组合的混合握手，以兼顾现有兼容性与新威胁模型。但“混合”策略需由正式协议和经过审查的实现来规定，不能自行把两份密钥拼起来就认为更安全。标准会更新勘误与实现建议，部署者应跟进权威来源。\n\nML-KEM 的作用，是为未来密钥协商提供标准化的后量子选项。理解它时要分清三件事：它建立共享秘密，实际数据通常交给对称算法加密，整体安全性还依赖协议和实现共同正确。\n\n来源：[NIST FIPS 203：Module-Lattice-Based Key-Encapsulation Mechanism](https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F203\u002Ffinal)","\u002Fuploads\u002F2026-10-17\u002F7cb94859-ea46-4839-bc88-b02008227f15.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},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse",{"id":32,"name":33,"slug":34},"8d35e42e-9f5b-4dd9-b30f-dc2c53d06096","硬件","hardware","NIST FIPS 203","https:\u002F\u002Fcsrc.nist.gov\u002Fpubs\u002Ffips\u002F203\u002Ffinal","published",null,false,56,0,"2026-10-17T00:00:00.000Z","2026-10-17T03:08:50.484Z",[45,54,63],{"id":46,"type":6,"title":47,"slug":48,"summary":49,"coverUrl":50,"authorName":14,"sno":51,"publishedAt":52,"createdAt":53},"d4a1ef13-fa42-41f3-a9d2-635f47d801d0","RISC-V PMP：处理器怎样给不同特权级划出内存禁区？","riscv-pmp-physical-memory-protection","RISC-V PMP 由高特权级软件配置物理内存区域访问规则，并由处理器在较低权限代码访问时执行检查。本文区分 PMP 与虚拟内存，介绍它在固件和嵌入式安全中的作用及实现边界。","\u002Fuploads\u002F2026-10-13\u002Fecfdd306-c8d2-4bfa-984e-7f579fd86f61.jpg",41,"2026-10-13T00:00:00.000Z","2026-10-13T02:13:39.212Z",{"id":55,"type":6,"title":56,"slug":57,"summary":58,"coverUrl":59,"authorName":14,"sno":60,"publishedAt":61,"createdAt":62},"56b94746-1551-4111-a1e9-6dc7e62e1604","RDMA：两台机器能否让网卡直接搬运注册内存？","rdma-registered-memory-and-remote-access","RDMA 让网卡在授权和注册内存范围内处理远端数据搬运。本文解释内存注册、访问权限与完成队列，避免把它误解为完全没有 CPU 参与。","\u002Fuploads\u002F2026-10-06\u002F86d526f9-9a46-46aa-8c81-1efd4aae1284.jpg",49,"2026-10-06T00:00:00.000Z","2026-10-06T07:51:32.204Z",{"id":64,"type":6,"title":65,"slug":66,"summary":67,"coverUrl":68,"authorName":14,"sno":69,"publishedAt":42,"createdAt":70},"67ba2085-7ee6-4379-9d0c-6372fed783ae","Intel TDX：云服务器管理员也看不到虚拟机里的数据吗？","intel-tdx-confidential-vm-explained","Intel TDX 通过处理器支持的隔离机制，将虚拟机运行环境划成受保护的 Trust Domain，降低宿主软件直接读取或篡改其内存的机会。本文说明机密计算解决什么信任问题，也谈远程证明、侧信道和来宾系统自身的风险。","\u002Fuploads\u002F2026-10-17\u002Ff8891699-ca7f-4edb-b64d-1b4db6421b0e.jpg",50,"2026-10-17T03:08:39.718Z"]