News for hackers. Stuff that matters.
Re:Incident with GitHub Actions and Codespaces by cyberpunk on Thursday April 14, 2022 @04:05AM (#31024415)
> automatic APT upgrades

Please, please don't ever do this. Or if you do, make sure you're taking a snapshot of the box every hour or something..

Re:Incident with GitHub Actions and Codespaces by FooBarWidget on Thursday April 14, 2022 @06:54AM (#31025224)
If you don't have a dedicated sysadmin who's always on top of new Gitlab versions, then the alternative to automatic upgrades is letting insecure versions run for an arbitrary time until someone takes the time to upgrade. Gitlab is merely 1 of the 200 things we have to keep track of.

Besides, we already make weekly automatic backups, stored remotely and encrypted. And Gitlab automatically makes a locally-stored backup before each upgrade, which is good enough unless the disk fails right after we discover that the upgrade is broken.

Re:Incident with GitHub Actions and Codespaces by vorpalhex on Thursday April 14, 2022 @09:50AM (#31026978)
You can configure just security patches and not full upgrades.
Re:Incident with GitHub Actions and Codespaces by heurisko on Thursday April 14, 2022 @04:28AM (#31024527)
What about automatic security APT updates?
Re:Incident with GitHub Actions and Codespaces by dgb23 on Thursday April 14, 2022 @04:08AM (#31024429)
Or just before the upgrade?
Re:Incident with GitHub Actions and Codespaces by mikepurvis on Thursday April 14, 2022 @06:50AM (#31025197)
That's how we do it— snapshot the box, apt dist-upgrade, snapshot again, gitlab upgrade, snapshot again.

A few days later, drop the snapshots.