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

    • tarneo@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      2 years ago

      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.

  • ReversalHatchery@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    2 years ago

    While we are here: what do you think about unattended updates on Debian and such? (as such being derivatives, including Proxmox VE)