Embedded Linux Security: Dr Jekyll and Mr Hyde
summary
Covers concrete failures on embedded devices: shipping with old kernels and unpatchable closed‑source drivers, apps running as root because dependencies break under upgrades, and automatic configuration that silently disables confinement. Recommends using Linux permissions, encryption and integrity (file system + attestation), and practical confinement with namespaces and seccomp, plus enforcing Verified Boot to stop tampered images. Shows real client cases where applying least privilege and patchable stacks prevents repeated field compromises.
AI-written summary · about
chapters (7)
- 0:00Embedded Linux security intro
- 2:20Dual nature of Linux security
- 6:48Linux security pros and cons
- 12:06Embedded security challenges
- 18:29Updating embedded software
- 25:21Managing permissions
- 29:39Balancing security and features
related talks
32mEmbedded Linux Security: Dr Jekyll and Mr Hyde
59mGetting Started with Embedded Linux Security
32mELC 2013 Security: Best Practices for Embedded Systems
45mNavigating Security Tradeoffs in Embedded Linux Systems
53mSecure Embedded Linux Product - A Success Story
42mSecurity in Large Scale Embedded Linux Projects
41mThinking Outside the (Linux) Box: Security Considerations From Human Actors
06mLightning Talk: Security Down to the Kernel