Comment on How do you keep track of vulnerabilities?
eager_eagle@lemmy.world 5 weeks agothat’s a lot of FUD, topgrade just upgrades all package managers you have, it doesn’t do the upgrades itself bypassing the package authors
Comment on How do you keep track of vulnerabilities?
eager_eagle@lemmy.world 5 weeks agothat’s a lot of FUD, topgrade just upgrades all package managers you have, it doesn’t do the upgrades itself bypassing the package authors
NaibofTabr@infosec.pub 5 weeks ago
The issue is more that trying to upgrade everything at the same time is a recipe for disaster and a troubleshooting nightmare. Once you have a few interdependent services/VMs/containers/environments/hosts running, what you want to do is upgrade them separately, one at a time, then restart that service and anything that connects to it and make sure everything still works, then move on to updating the next thing.
If you do this shotgun approach for the sake of expediency, what happens is something halfway through the stack of upgrades breaks connectivity with something else, and then you have to go digging through the logs trying to figure out which piece needs a rollback.
Even more fun if two things in the same environment have conflicting dependencies, and one of them upgrades and installs its new dependency version and breaks whatever manual fix you did to get them to play nice together before.
eager_eagle@lemmy.world 5 weeks ago
I’ve been doing that for years. Rollbacks are very rare, to the point that it doesn’t make much of a difference whether I do them all at once or not, other than spending more time to do it.
If I wasn’t using containers for everything sure. Otherwise it’s a bit of an excessive concern.