• 4 Posts
  • 11 Comments
Joined 2 years ago
cake
Cake day: March 3rd, 2023

help-circle

  • 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.









  • Main computer: Arch (BTW) because I am a WM user (awesomewm) and AL has no bloat to remove. Also because of the AUR.

    Servers:

    • main server is a gentoo beast. I chose gentoo because systems was actually causing some problems and reporting a “degraded” status. OpenRC is really nice after years of systemd :-)
    • second server, used for backups: NixOS, for no particular reason. I might install Debian 12 on it one day.