Sustaining Yesterday’s Linux: Delivering Security for Today’s Workloads
summary
Long-term maintenance teams track upstream CVEs, assess applicability with a 0–10 severity score, and perform targeted backporting CVEs into decade-old kernels, libraries and distro stacks that no longer match upstream. Engineering work includes reworking patches to preserve ABI/API stability, rebuilding vendor binaries, and shipping high-severity fixes (example: an old Docker CVE patched and delivered in about 5 business days for a global bank), avoiding full re‑certification and keeping mission systems running.
AI-written summary · about
chapters (8)
- 0:00Sustaining legacy Linux
- 1:07Why Linux runs decades
- 2:54Constraints on OS upgrades
- 5:03Upgrade vs staying current
- 7:09Sustaining engineering secures legacy
- 9:13Backported fixes and compliance
- 10:57Controlled modernization benefits
- 11:42Q&A
related talks
35mKeeping the linux kernel secure across 10+ RHEL releases
20mPrioritizing the Linux OS Hardening and CVE Mitigation
26mEngineering for the Long Haul: Operating Open Source at Scale
21mFrom CVEs To Compliance: Automating Embedded Linux Kernel Security
39mFrom Discovery to Fix: What 10,000 Open Source Projects Reveal About CVE Remediation
41mChallenges Around Long-Term Kernel Maintenance
51m10 Years of Linux Security - A Report Card
21mDevSecOops: 15 years of DevOps and patching is still horrible