Tl;dr: Automatic updates on my home server caused 8 hours of downtime of all of renn.es’ docker services including email and public websites
deleted by creator
[This comment has been deleted by an automated system]
deleted by creator
[This comment has been deleted by an automated system]
I’m surprised this strategy was approved for a public server
The goal was to avoid getting hacked on a server that could have many vulnerable services (there are more than 20 services on there). When I set this up I was basically freaked out by the fact I hadn’t updated mastodon more than a week after the last critical vulnerability in it was found (arbitrary code execution on the server). The quantity of affected users, compared to the impact it would have if hacked, made me choose the option of auto-updates back then, even if I now agree it wasn’t clever (and I ended up shooting myself I’m the foot). These days I just do updates semi-regularly and I am subscribed to mailing lists like oss-security to know there’s a vulnerability as early as possible. Plus I am not the only person in charge anymore.
deleted by creator
I don’t want to seem rude, but in my opinion automated unattended updates on Gentoo is a bad idea.
While we are here: what do you think about unattended updates on Debian and such? (as such being derivatives, including Proxmox VE)
deleted by creator