[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"legal-e2ee-zh":3},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":9,"body":10,"_type":446,"_id":447,"_source":448,"_file":449,"_stem":450,"_extension":451},"\u002Flegal\u002Fe2ee\u002Fzh","e2ee",false,"","我们的端到端加密如何工作","更新时间：2026年6月",{"type":11,"children":12,"toc":435},"root",[13,20,25,31,56,61,66,71,75,80,85,129,134,162,182,194,198,203,209,221,233,238,244,256,268,272,277,282,323,328],{"type":14,"tag":15,"props":16,"children":17},"element","h1",{"id":8},[18],{"type":19,"value":8},"text",{"type":14,"tag":21,"props":22,"children":23},"p",{},[24],{"type":19,"value":9},{"type":14,"tag":26,"props":27,"children":29},"h2",{"id":28},"简而言之",[30],{"type":19,"value":28},{"type":14,"tag":32,"props":33,"children":34},"ul",{},[35,41,46,51],{"type":14,"tag":36,"props":37,"children":38},"li",{},[39],{"type":19,"value":40},"你的数据在你的设备上加密，只以不可读的密文形式离开设备。我们的服务器仅存储加密的Blob，无法访问明文。",{"type":14,"tag":36,"props":42,"children":43},{},[44],{"type":19,"value":45},"所有密钥都是从一个128位恢复码衍生的，该恢复码永远不会离开你的设备。我们不知道它，也无法恢复它。",{"type":14,"tag":36,"props":47,"children":48},{},[49],{"type":19,"value":50},"每个Record都用自己的密钥加密，在解密前要进行真实性检查（使用Ed25519的Verify-before-Decrypt）。",{"type":14,"tag":36,"props":52,"children":53},{},[54],{"type":19,"value":55},"E2EE并非保护一切：某些元数据（数据量、访问时间）仍然可见，而且被破坏的设备或丢失的恢复码无法通过密码学挽救。",{"type":14,"tag":26,"props":57,"children":59},{"id":58},"端到端在我们这里意味着什么",[60],{"type":19,"value":58},{"type":14,"tag":21,"props":62,"children":63},{},[64],{"type":19,"value":65},"端到端加密意味着：你数据的明文仅存在于你自己的设备上。加密和解密完全在本地进行。在设备间同步和存储在我们服务器上的内容总是在离开设备前已加密。",{"type":14,"tag":21,"props":67,"children":68},{},[69],{"type":19,"value":70},"具体来说：一条数据行在客户端规范地编码为JSON，然后用AEAD方法加密。服务器只接收一个不透明的字节Blob加一些管理字段。服务器不拥有解密所需的任何密钥。这是一个架构特性，而非承诺：由于密钥永不到达服务器，服务器在技术上无法读取内容。",{"type":14,"tag":72,"props":73,"children":74},"e2ee-flow-diagram",{},[],{"type":14,"tag":26,"props":76,"children":78},{"id":77},"你的数据如何被加密",[79],{"type":19,"value":77},{"type":14,"tag":21,"props":81,"children":82},{},[83],{"type":19,"value":84},"我们使用来自@noble\u002Fciphers、@noble\u002Fhashes和@noble\u002Fcurves库的久经考验、标准化的构建块：",{"type":14,"tag":32,"props":86,"children":87},{},[88,99,109,114,124],{"type":14,"tag":36,"props":89,"children":90},{},[91,97],{"type":14,"tag":92,"props":93,"children":94},"strong",{},[95],{"type":19,"value":96},"AES-256-GCM",{"type":19,"value":98},"加密你的Records。AES-256-GCM是一个AEAD方法，同时确保机密性（没人能读取）和完整性（篡改会被发现）。每个Record使用一个随机的12字节Nonce和一个16字节的认证码（MAC）。格式：nonce(12) ‖ ciphertext ‖ mac(16)。",{"type":14,"tag":36,"props":100,"children":101},{},[102,107],{"type":14,"tag":92,"props":103,"children":104},{},[105],{"type":19,"value":106},"XChaCha20-Poly1305",{"type":19,"value":108},"在设备配对时加密密钥材料（Key-Wrapping）。它也是一个AEAD方法，但使用较长的24字节Nonce，使得随机Nonce不成问题。",{"type":14,"tag":36,"props":110,"children":111},{},[112],{"type":19,"value":113},"**AAD（Associated Data）**将每个密文绑定到其元数据——头、Bucket、Record-UUID、Revision、Key-Epoch、Schema版本和填充长度。这些字段是共认证的：即使其中一个被修改，解密也会失败。空AAD被严格拒绝（Confused-Deputy防护）。",{"type":14,"tag":36,"props":115,"children":116},{},[117,122],{"type":14,"tag":92,"props":118,"children":119},{},[120],{"type":19,"value":121},"Padding",{"type":19,"value":123},"隐藏确切大小：每个Record都被填充到Bucket大小（256、1024、4096、16384或65536字节；超过这个范围则为65536的倍数）。因此Blob大小只表示一个粗略等级，而非确切的数据量。",{"type":14,"tag":36,"props":125,"children":126},{},[127],{"type":19,"value":128},"**Ed25519签名（blob_sig）**对每个Blob进行签名。在每次解密前，客户端根据授权的设备密钥验证此签名（Verify-before-Decrypt）。验证以RFC-8032严格模式运行（zip215:false），这排除了通过Low-Order点伪造。篡改的数据立即产生错误，无静默缺陷。",{"type":14,"tag":26,"props":130,"children":132},{"id":131},"你的密钥留在你的设备上",[133],{"type":19,"value":131},{"type":14,"tag":21,"props":135,"children":136},{},[137,139,144,146,151,153,160],{"type":19,"value":138},"一切的根源是一个",{"type":14,"tag":92,"props":140,"children":141},{},[142],{"type":19,"value":143},"128位恢复熵",{"type":19,"value":145},"——恢复码。从这16个随机字节，使用",{"type":14,"tag":92,"props":147,"children":148},{},[149],{"type":19,"value":150},"HKDF-SHA256",{"type":19,"value":152},"（一个密钥衍生函数，从一个秘密产生许多域隔离的密钥）确定地衍生Master-Secret，以及进一步的密钥：一个Account-ID、一个密钥加密密钥、认证密钥（authSeed）和路由密钥。每个衍生过程使用自己的、版本化的标签（例如",{"type":14,"tag":154,"props":155,"children":157},"code",{"className":156},[],[158],{"type":19,"value":159},"mypep\u002Fmaster\u002Fv1",{"type":19,"value":161},"），所以密钥不会重叠。",{"type":14,"tag":21,"props":163,"children":164},{},[165,167,172,174,180],{"type":19,"value":166},"每个Collection有自己的Collection-Key，",{"type":14,"tag":92,"props":168,"children":169},{},[170],{"type":19,"value":171},"每个Record和Revision",{"type":19,"value":173},"有自己的Record-Key（",{"type":14,"tag":154,"props":175,"children":177},{"className":176},[],[178],{"type":19,"value":179},"rec\u002F\u003Cuuid>\u002F\u003Crev>",{"type":19,"value":181},"）。这种(Record, Revision)的每个密钥确保完全的密钥隔离：没有AES-GCM密钥被使用两次——这是针对Nonce重用攻击的强大防护。",{"type":14,"tag":21,"props":183,"children":184},{},[185,187,192],{"type":19,"value":186},"Master-Secret有意",{"type":14,"tag":92,"props":188,"children":189},{},[190],{"type":19,"value":191},"不被存储",{"type":19,"value":193},"。本地仅存储衍生的值和设备特定的签名\u002F包装密钥——在浏览器中存储在IndexedDB。",{"type":14,"tag":195,"props":196,"children":197},"key-derivation-diagram",{},[],{"type":14,"tag":21,"props":199,"children":200},{},[201],{"type":19,"value":202},"**Recovery——特性和责任：**整个密钥树取决于恢复码。我们不存储它；后门、密钥托管或服务器端重置在架构上被排除——不仅是政策问题，而是因为密钥在技术上永不到达服务器。这是真正E2EE的核心：除你之外——即使是我们——都无法在没有恢复码或配对设备的情况下恢复你的数据。如果码丢失且不存在已配对的设备，数据将永久无法访问。",{"type":14,"tag":26,"props":204,"children":206},{"id":205},"我们的服务器看到什么以及什么不看到",[207],{"type":19,"value":208},"我们的服务器看到什么——以及什么不看到",{"type":14,"tag":21,"props":210,"children":211},{},[212,214,219],{"type":19,"value":213},"服务器仅存储加密的Blob。它",{"type":14,"tag":92,"props":215,"children":216},{},[217],{"type":19,"value":218},"看不到",{"type":19,"value":220},"：你Records的内容、你Collections的名称（它们仅显示为不透明的HMAC-SHA256-Bucket）或你的密钥。",{"type":14,"tag":21,"props":222,"children":223},{},[224,226,231],{"type":19,"value":225},"坦诚地说，它确实看到",{"type":14,"tag":92,"props":227,"children":228},{},[229],{"type":19,"value":230},"一些元数据",{"type":19,"value":232},"：不透明的Bucket值、Record修订、通过Padding的粗略大小等级、同步频率、设备ID（作为设备密钥的SHA-256哈希）和同步时的游标位置。从中可以推断一个账户是活跃的，以及大约多少和多大的数据何时移动——但不是内容是什么。",{"type":14,"tag":21,"props":234,"children":235},{},[236],{"type":19,"value":237},"冲突解决纯粹通过Revision进行（更高的Revision赢，\"Last-Write-Wins\"），因为服务器不了解内容且不能进行内容级别的合并。认证通过Ed25519的Challenge-Response进行，随后是JWT令牌；设备列表用你的Auth-Key签名，仅在客户端验证。",{"type":14,"tag":26,"props":239,"children":241},{"id":240},"多个设备配对",[242],{"type":19,"value":243},"多个设备（配对）",{"type":14,"tag":21,"props":245,"children":246},{},[247,249,254],{"type":19,"value":248},"一个新设备，比如浏览器，通过",{"type":14,"tag":92,"props":250,"children":251},{},[252],{"type":19,"value":253},"QR码与手机配对",{"type":19,"value":255},"。QR码直接传输浏览器的公共设备密钥（带外），不通过服务器——这保护密钥交换免受中间人攻击。手机用X25519-ECDH和XChaCha20-Poly1305将Identity-Bundle（账户数据密钥、Auth-Key、Account-ID、路由密钥）仅为浏览器打包并加密传输。",{"type":14,"tag":21,"props":257,"children":258},{},[259,261,266],{"type":19,"value":260},"解密后，浏览器显示一个",{"type":14,"tag":92,"props":262,"children":263},{},[264],{"type":19,"value":265},"指纹",{"type":19,"value":267},"（Account-ID的SHA-256，作为十六进制分组）。如果它与手机上的显示一致，就确保了你收到了正确的Bundle。网络客户端没有自己的恢复码：在浏览器存储丢失时，你只需再次与手机配对。",{"type":14,"tag":269,"props":270,"children":271},"pairing-diagram",{},[],{"type":14,"tag":26,"props":273,"children":275},{"id":274},"这不保护什么",[276],{"type":19,"value":274},{"type":14,"tag":21,"props":278,"children":279},{},[280],{"type":19,"value":281},"E2EE很强大，但不是万能的。老实地面对限制：",{"type":14,"tag":32,"props":283,"children":284},{},[285,290,295,300,313,318],{"type":14,"tag":36,"props":286,"children":287},{},[288],{"type":19,"value":289},"**被破坏的设备：**浏览器上下文中的恶意软件或对IndexedDB的直接访问可以读取本地存储的密钥，从而解密一切。本地数据库以明文形式存在。",{"type":14,"tag":36,"props":291,"children":292},{},[293],{"type":19,"value":294},"**丢失的恢复码：**没有码和没有配对设备就没有回头路。不存在密钥轮换和备份机制。",{"type":14,"tag":36,"props":296,"children":297},{},[298],{"type":19,"value":299},"**元数据：**数据量、大小等级、访问模式和时间戳对服务器仍然可见。",{"type":14,"tag":36,"props":301,"children":302},{},[303,305,311],{"type":19,"value":304},"**照片Blob：**照片是内容寻址的（",{"type":14,"tag":154,"props":306,"children":308},{"className":307},[],[309],{"type":19,"value":310},"blob_id = sha256(blob)",{"type":19,"value":312},"）。拥有明文的人可以检查是否上传了确切的照片。",{"type":14,"tag":36,"props":314,"children":315},{},[316],{"type":19,"value":317},"**恶意服务器：**它无法读取或伪造内容（Verify-before-Decrypt保护），但它可以扣留数据或重新传输旧的已签名设备列表（Replay）。这种Replay的损害是有限的：设备以幂等方式注册，所以重放的旧列表不会覆盖当前状态。服务器无法发明新的有效数据。",{"type":14,"tag":36,"props":319,"children":320},{},[321],{"type":19,"value":322},"**Auth-Key：**任何获得Auth-Key的人都可以更改设备列表并重新认证。它必须保持秘密。",{"type":14,"tag":26,"props":324,"children":326},{"id":325},"密码学构建块概览",[327],{"type":19,"value":325},{"type":14,"tag":32,"props":329,"children":330},{},[331,340,349,366,375,385,395,405,415,425],{"type":14,"tag":36,"props":332,"children":333},{},[334,338],{"type":14,"tag":92,"props":335,"children":336},{},[337],{"type":19,"value":96},{"type":19,"value":339},"——Record加密（AEAD）；12字节Nonce，16字节MAC。",{"type":14,"tag":36,"props":341,"children":342},{},[343,347],{"type":14,"tag":92,"props":344,"children":345},{},[346],{"type":19,"value":106},{"type":19,"value":348},"——配对时的Key-Wrapping（AEAD）；24字节Nonce，16字节MAC。",{"type":14,"tag":36,"props":350,"children":351},{},[352,357,359,364],{"type":14,"tag":92,"props":353,"children":354},{},[355],{"type":19,"value":356},"Argon2id v1.3",{"type":19,"value":358},"——基于密码的内存硬化衍生（标准：64 MiB、3次迭代、4条通道）；可用于未来的基于密码的功能，但",{"type":14,"tag":92,"props":360,"children":361},{},[362],{"type":19,"value":363},"不",{"type":19,"value":365},"用于恢复码——恢复码已经是128位随机熵，不需要内存硬化。",{"type":14,"tag":36,"props":367,"children":368},{},[369,373],{"type":14,"tag":92,"props":370,"children":371},{},[372],{"type":19,"value":150},{"type":19,"value":374},"——从恢复码衍生所有密钥，通过版本化标签进行域隔离；32字节输出。",{"type":14,"tag":36,"props":376,"children":377},{},[378,383],{"type":14,"tag":92,"props":379,"children":380},{},[381],{"type":19,"value":382},"HMAC-SHA256",{"type":19,"value":384},"——Collections的不透明路由（Bucket计算）。",{"type":14,"tag":36,"props":386,"children":387},{},[388,393],{"type":14,"tag":92,"props":389,"children":390},{},[391],{"type":19,"value":392},"SHA-256",{"type":19,"value":394},"——指纹、设备ID和照片寻址的哈希。",{"type":14,"tag":36,"props":396,"children":397},{},[398,403],{"type":14,"tag":92,"props":399,"children":400},{},[401],{"type":19,"value":402},"Ed25519（RFC-8032-严格，zip215:false）",{"type":19,"value":404},"——Records、设备列表和认证的签名。",{"type":14,"tag":36,"props":406,"children":407},{},[408,413],{"type":14,"tag":92,"props":409,"children":410},{},[411],{"type":19,"value":412},"X25519-ECDH",{"type":19,"value":414},"——设备配对时的密钥交换。",{"type":14,"tag":36,"props":416,"children":417},{},[418,423],{"type":14,"tag":92,"props":419,"children":420},{},[421],{"type":19,"value":422},"Padding-Buckets",{"type":19,"value":424},"（256 B至65536 B，超过则为65536的倍数）——大小混淆。",{"type":14,"tag":36,"props":426,"children":427},{},[428,433],{"type":14,"tag":92,"props":429,"children":430},{},[431],{"type":19,"value":432},"密钥长度",{"type":19,"value":434},"始终为32字节（256位）。",{"title":7,"searchDepth":436,"depth":436,"links":437},2,[438,439,440,441,442,443,444,445],{"id":28,"depth":436,"text":28},{"id":58,"depth":436,"text":58},{"id":77,"depth":436,"text":77},{"id":131,"depth":436,"text":131},{"id":205,"depth":436,"text":208},{"id":240,"depth":436,"text":243},{"id":274,"depth":436,"text":274},{"id":325,"depth":436,"text":325},"markdown","content:legal:e2ee:zh.md","content","legal\u002Fe2ee\u002Fzh.md","legal\u002Fe2ee\u002Fzh","md"]