Matrix Cryptographic Key Infrastructure
summary
Clear description of how Matrix moves the room encryption key (Megolm session) between devices: either direct encrypted m.room_key to-device events or server-side key backup using AES + HKDF + ECDH to wrap per-session secrets. Device identity uses a chain of signatures — device key → self-signing key → master key → user-signing key — so one master key anchors trust. Backup recovery depends on a user-held recovery key; there is a known Mac bug passes nil in older clients that weakens integrity checks.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:48Cryptography in Matrix
- 7:53Basic Cryptography Primitives
- 14:57Key Sharing Mechanisms
- 18:53Key Backup System
- 26:25Device Verification
- 33:15Key Storage Solutions
- 38:14Summary and Takeaways
- 39:24Q&A Session
related talks
42mDesigning Matrix: A Global Decentralised End-to-End Encrypted..
34mPractically-exploitable Cryptographic Vulnerabilities in Matrix
51mKey Management 101: DEKs, KEKs, and Credentials Living Together, Oh My!
37mKeys from the castle: ancient art of managing keys and trust
15mEncryption at Rest – Master Key Based on a Hybrid KEM
24mEnd-to-End encryption for iOS Developer
24mRelying Party Security
38mHow to Distribute Keys Securely for 20% of the Web