IoT TLS: Why It's Hard
summary
Constrained IoT devices (hundreds of KB RAM, ~1 MB flash, 10–100 MHz CPUs) can barely run TLS and often fail on three practical points: poor entropy makes client keys trivially guessable, certificate stores consume hundreds of KB (typical browser roots ~200 KB, Google offers ~60 KB), and TLS buffer/record sizes (16 KB) exceed tiny buffers. Zephyr integrates mbed TLS via a new sockets-with-TLS layer that hides complex init steps but remains transitional; offload hardware and DTLS add extra pitfalls.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 0:50What is IoT
- 2:19Google Search
- 2:43Worst Examples
- 3:32James Mickens
- 4:07We have a solution
- 4:47IoT is vast
- 5:37Smart fridges
- 6:00Tiny devices
- 7:08IoT toaster
- 8:10TLS
- 8:22Networking Stacks
- 9:57TLS Explained
- 17:09Summary
- 17:47Memory
- 23:44Stream of abstraction
- 25:27Why F
- 26:26Complicated API
- 28:14Effort Concerns
related talks
42mCryptography Support in Zephyr: Recent Changes and Upcomings
20mPost-Quantum Cryptography for the Internet of Things- 42mCryptography Support in Zephyr: Recent Changes and Upcomings
35mIoT Cornerstones of Security
34mX.509 Client Authentication in Zephyr
35mEnd-to-end IoT Development with Zephyr
26mHypervisors and IoT (IoT Secret Storage)
23mKeynote: Zephyr & IoT Security