This Shit is Hard: Fixing Python Library Security Issues at Scale
Share
Patching a CVE in a Python library sounds simple... until you try to do it at scale.
Engineer Wesley Wiedenmeier breaks down why backporting security fixes is so much harder than it looks. You have to track down trustworthy upstream patches, wrangle years-old dependency trees just to run a test suite, prove an exploit is actually fixed, and even build your own "diff of diffs" tool to review backported patches safely.
It's a great reminder of how much invisible engineering goes into keeping the software supply chain secure. Read it here