End-to-End encryption for iOS Developer
summary
Explains concrete E2EE mechanics for iOS: uses prekeys and signatures for authentication, rotate keys with each message and keep ~20–30 previous keys to handle out-of-order delivery, advance hashes up to ~1,000 steps for efficiency, and derive signing keys from shared secrets to avoid device-forensics. Covers iOS workarounds: wipe APNs (silent push → background fetch → fetch encrypted payload), remove image metadata and exclude data from iTunes/iCloud backups. Notes group-costs: a 1 KB message to 100 participants can become ~500 KB uploaded, and MLS aims to scale to ~1,000 participants.
AI-written summary · about
chapters (5)
- 0:00Introduction and motivation
- 2:58What is end-to-end encryption
- 9:23iOS app privacy pitfalls
- 15:49Future of encrypted messaging
- 17:15Q&A session
related talks
05mEnd to End Encryption for Mobile Developers
50mBuilding Production-Grade End to End Encrypted App...
41mNote encryption: 10 lines for encryption, 1500 lines for key management
58m10 Lines of Encryption, 1500 Lines of Key Management
40mEnd-to-end encryption: Behind the scenes- 58m10 Lines of Encryption, 1500 Lines of Key Management
28mApp Security Essentials
10miOS present and future