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

    It’s a concern even with a reverse proxy. The reverse proxy encrypts your connection from A to B, but does nothing to stop the various security concerns that have been noted. Because those concerns don’t rely on intercepting unencrypted traffic. If you can reach Jellyfin’s main log in page, you can exploit it. Full stop.

    The only way a reverse proxy would stop someone from being able to exploit it is to include a separate login on your reverse proxy, meaning attackers wouldn’t even be able to hit Jellyfin’s landing page unless they know your proxy’s password. But notably, this breaks basically everything except for browsers. All of your smart TVs, mobile apps, etc would stop functioning, because they’d bounce off of that reverse proxy login page.

    • kata1yst@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      21 hours ago

      I don’t proxy the port, I proxy the routes needed for auth and interface. This isn’t that hard.

      EDIT: ah I see what you’re saying, you’re talking about the app surface rather than the raw admin API. The risk is small enough with the remaining attack surface that I’m not particularly worried, though obviously I’d like it to be better.