Working on Quantum-Safe Encrypted Emails
summary
Project implements post-quantum email encryption that interoperates with Office365 and Gmail by encrypting message bodies and attachments client-side with MLKM (768), delivering keys from a centralized key manager running in Azure confidential compute and authenticating recipients via single sign-on auth rather than PKI. Add-ins inject JavaScript to encapsulate/decap on send and open, keeping recipients and subjects plaintext for routing, avoiding key distribution, and achieving end-to-end protection against harvest-now-decrypt-later.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:27Building quantum-safe email
- 2:49Harvestable email data
- 4:32Harvest now decrypt later
- 6:00Email as data repository
- 6:43PKI limits for email
- 9:11Encrypted email use cases
- 10:53Solution requirements
- 12:36ML-KEM encryption
- 14:44Key management with auth
- 17:16End-to-end beyond TLS
- 19:29TE module key management
- 21:14Email flow architecture
- 23:45Email client integration
related talks
30mPost-Quantum Crypto Integration for Enterprise Applications
31mHybrid PQC E-Mail Communication: Easing Migration Pain
36mPost-Quantum Cryptography for Digital Signing
27mPost-Quantum Cryptography
22mEfail: Breaking S/MIME and OpenPGP Email Encryption using Exfiltration Channels
06mKeynote: Evolutions in data privacy: threats and opportunities
53mPanel: Migrating to Post-Quantum Schemes
22mgRPC and Post-Quantum Cryptography