• hperrin@lemmy.ca
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    6 hours ago

    I’ve had my instance open to the internet for about two years with no issues.

      • hperrin@lemmy.ca
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        6 hours ago

        I mean, the worst that could happen is they delete everything on the server and I have to spend time restoring from a backup. Not exactly the riskiest thing to do.

        • frongt@lemmy.zip
          link
          fedilink
          English
          arrow-up
          3
          ·
          4 hours ago

          Well, the worst that could happen is they start hosting CSAM out of your house and then the FBI knocks on your door.

        • Appoxo@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 hours ago

          I am using a non-privileged user on jellyfin.
          Admin stuff needs to be done with a hidden user.
          I might should be bothering to do rootless docker at some point…

    • Pika@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      3 hours ago

      depending what is on it, and your risk factor, theoretically an attacker can check known resource paths to confirm or deny whats on the server. That’s my main complaint currently on it is that the jellyfin team is aware of the fact that it doesn’t need authentication, but are looking for some miracle solution that won’t toss legacy clients out in order to fix, so therefore the issues are just perpetually open.

      edit: it looks like some of these issues may be being worked on now that they moved the problemic protocal into a plugin. I hope that that means they will close them in the next few releases!