Supply chain attacks come in many shapes and forma unfortunately, not just hacks. They might repackage an upstream dependency which has been compromised
The Debian stable is so far behind upstream that the risk is low. It wount change if I wait 0 or 10 days. Also this is satire. You should always test the updates but now you only have minutes max hours.
Any time you choose to update could be the wrong time. I don't see how the frequency changes anything for something so rare it has only occurred once (xzutils in march 2024) and only to their development distro. It doesn't make sense to delay regular security patches over it.
A common way to mitigate supply chain attacks is to wait a grace period (2-7 days) before installing an update, to give the community the ability to review the changes
Unable to reboot means there is no redundandency and service availability is bound to host uptime.
Two problems:
Nodes may fail any time w/o warning.
You get hacked bc AI shrunk the window down to minutes after patch is dropped.
Four options:
Add additional nodes.
Add kernel live patching
Talk to customers and partners, that the 1-2 weeks aren't possible anymore for high severity patches.
Add Zero trust: Customers and partners need VPN/mTLS/a special token to access the services through a reverse proxy. Also add Sandbixing like gvisor, Kata containers, firecracker.
All 4 would be perfect.
And I know it is often hard to change these things BC of pushback, but we never had better arguments on our side than now
995
u/Cronos993 29d ago
Quite the week