Collection of potential security issues in Jellyfin This is a non exhaustive list of potential security issues found in Jellyfin. Some of these might cause controversy. Some of these are design fla…

  • paperemail@links.rocks
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    2 days ago

    Not unless the reverse proxy adds some layer of authentication as well. Something like HTTP basic auth, or mTLS (AKA 2-way TLS AKA client certificates)

    For nginx: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/

    so if I add a user ”john” with password “mypassword” to video.example.com, you can try adding the login as: “https://john:mypassword@video.example.com”/

    Most HTTP clients (e.g. browsers) support adding login like that. I don’t know what other jellyfin clients do that.

    The other option is to set up a VPN (I recommend wireguard)

    • jagged_circle@feddit.nl
      link
      fedilink
      English
      arrow-up
      2
      ·
      15 hours ago

      You can’t do that with jellyfin.

      Basic auth doesn’t work with jellyfin. Its a bug. Enable it on your reverse proxy, and jellyfin breaks. Devs closed it as wontfix

    • Saik0@lemmy.saik0.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      21 hours ago

      Not unless the reverse proxy adds some layer of authentication as well.

      This is correct. However I’d want to add, that this will break EVERY app-based access of jellyfin which defeats the purpose for a lot of people. Adding auth in front of jellyfin will work and allow you to use the web client only.

      You kind of touched on it… I wanted to make it clear.

      VPN would be a better more interoperable answer for most cases, you’ll still be stuck on devices like WebOS on LG tvs, or roku devices, or others that don’t have the ability to install vpn clients.

      • jagged_circle@feddit.nl
        link
        fedilink
        English
        arrow-up
        1
        ·
        15 hours ago

        This is misinformation. It breaks the web app too.

        You can’t use basic auth with jellyfin at all. Its a bug. Jellyfin closed the bug as won’t fix because, it seems, they dont care about security.

        • Saik0@lemmy.saik0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 hours ago

          Oh, sure enough. Basic auth breaks the login function. I didn’t test it myself and didn’t think that it wouldn’t work for basic auth. I’ve put other auths in front of it and it works. So It’s not completely “misinformation”. Just annoying that the easiest most basic form of auth won’t work.

          • jagged_circle@feddit.nl
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            9 hours ago

            What other auths can you put in front of it?

            The problem is that they’re (ab)using the Auth header, which causes a colission and you can’t load many required assets.

            • Saik0@lemmy.saik0.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 hours ago

              I was testing a 2fa based one the other weak and jellyfin was the service I decided to test with. Ultimately didnt like it so I rolled ot back.I’d have to go look it up to get you a name.