No awards are needed, just wanted to share my excitement that while my Jellyfin server still keeps loosing my entire library every 24 hours at least now it has a domain and ssl cert!

That is all. Happy Friday everyone

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (10 children)

What's wrong with exposing Jellyfin to the internet?

  • source
  • parent
  • hideshow 10 child comments
  • [–] 9 points 1 year ago* (1 child)

    There are a few security issues with it, but all of the worst known issues require a valid login token. So an attacker would already need to have valid login credentials before they could actually do anything bad. Things like being able to stream video without authentication (but it requires already having a list of the stored media on the server, which means you have been logged in before). Or being able to change other users’ settings (but it requires already being logged in to a valid user).

    Basically, make sure you use good passwords, and actually trust any other users to do the same.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 1 year ago

    The bug you mentioned actually just requires the attacker knows your local media paths to generate the hash. The issue is that most people use trash guides to setup *arr which means they probably have the same paths for everything

  • source
  • parent
  • [–] 0 points 1 year ago (6 children)

    You really shouldn't expose anything directly to the internet. It is a security problem waiting to happen. (Assuming it hasn't already)

    This is how giant botnets form.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 1 year ago (5 children)
  • [–] 5 points 1 year ago (4 children)

    Bots randomly attack stuff, and if you leave something insecure, they'll install a bot net node.

  • source
  • parent
  • hideshow 4 child comments
  • [–] -2 points 1 year ago (3 children)
  • [–] 5 points 1 year ago (2 children)

    Default passwords, old insecure versions of apps and system packages, etc. "Just getting it working" usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago (1 child)

    Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall.

  • source
  • parent
  • hideshow 1 child comment