• mic_check_one_two@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    7
    ·
    8 hours ago

    There has been a known “anyone can access your media without authentication” vulnerability for seven years and counting, and the Jellyfin devs have openly stated that they have no intentions of fixing it. Because fixing it would require completely divesting from the Enby branch that the entire program is built upon. And they never plan on refactoring that entire thing, so they never plan on fixing the vulnerabilities.

    The “don’t expose it to the internet” people aren’t just screaming at clouds. Jellyfin is objectively insecure, and shouldn’t be exposed.

    • grrgyle@slrpnk.net
      link
      fedilink
      English
      arrow-up
      2
      ·
      5 hours ago

      Ahh bummer. It works so well as a home media server… kind of calls out for sharing.

    • kieron115@startrek.website
      link
      fedilink
      English
      arrow-up
      3
      ·
      edit-2
      6 hours ago

      Jeez, so it’s meant to be a literal home media server. Able, but not designed, to be used for sharing.

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

        Exactly. And that’s honestly why I doubt it will ever truly contend with Plex. It’s fine for sharing with friends who can figure out how to connect via VPN, but it’ll never be robust enough to share with your tech-illiterate grandparents on the open internet. Plex wins handily in that regard, because their sign in process is basically the same as Netflix, HBO, Hulu, etc…

        Plex has problems of its own, but (at least as of me writing this) it doesn’t have any major known security vulnerabilities. They had some level 10.0 vulnerability last year, but they followed standard CVE protocols and patched it before the vulnerability was actually released.