Paving the Way for Uninterrupted Car Operations
summary
FFI on containers with podman separates ASIL-critical services into an uninterfered partition and noncritical workload into a QM partition using namespaces, cgroup v2, systemd and SELinux, with CentOS Automotive/Fedora components and BlueC remote control. Demo shows a nested-container attack that tries to steal CPU priority but SELinux blocks privilege escalation, and bluecctl plus podman+systemd unit files stop, signal and recover services so vehicle indicators reflect failures and automated recovery works.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 0:43Freedom from interference
- 3:11ISO 26262 standards
- 6:29ASIL and quality levels
- 10:06CentOS Automotive overview
- 14:44Partitioning and isolation
- 16:30Systemd and BlueChi
- 17:14Boot and container startup
- 20:05Certification challenges
- 20:49Security demo: CPU hijacking
- 24:42Simulated attack demo
- 27:12BlueChi demo and monitoring
- 31:51QM service recovery
- 35:09Conclusion
related talks
40mContainers in a Car
35mValidating Freedom From Interference in Automotive Linux
46mSecuring Applications and Pipelines on a Container Platform
45mSELinux All the Way Down: Namespaces for SELinux
47mContainer Security
45mMaking Containers Safer
44mUsing SELinux with container runtimes
19mRootless containers with Podman