I just need to gush for a minute. I am about to shutdown my server in order to move it to the basement. This off the shelf $300 desktop running Pop!_OS is my self-hosting server that has dutifully done it’s job without a single complaint. It has been rebooted maybe three times since 2020 and it currently has an uptime of 840 days. That’s 840 days of not ever thinking about this thing. It self updates via Cron jobs and just…works.

I am afraid to open the box up though. Those dust bunnies must be huge.

  • hperrin@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    3 months ago

    How vulnerable your system is with an old kernel/old code depends on what you’re running. If you’re running a bunch of sophisticated services that allow access on the open internet, you may have more vulnerabilities than if you’re just running a file share. The kernel doesn’t really matter at all unless either you allow other people to run commands or someone is able to exploit a RCE exploit.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      3 months ago

      The kernel has tons of vulnerabilities that get patched with updates. You really shouldn’t be running a older kernel for that long

      • hperrin@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        3 months ago

        Sure, but those vulnerabilities aren’t just open to the network. Almost every one requires you to be able to run at least unprivileged arbitrary code on the machine.

          • hperrin@lemmy.world
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            3 months ago

            It’s usually very big news when there’s a vulnerability in the Linux kernel itself that can be remotely exploited. Like, everyone on any security show/podcast/blog is talking about it.