78
What's the security situation when opening a jellyfin server up for casting? (feddit.nu)
submitted 11 months ago by to c/selfhosted@lemmy.world
74 comments fedilink hide all child comments
 

when reading through the jellyfin with chromecast guide i realized that it would probably be less effort to just let the casting api be public, with the added bonus that i could then cast my library to any device that supports it. but that seems like it would paint a giant target on the server.

what's the recommended way of doing stuff like this? ideally i want to be able to go to someone's house and just play some of my media on their tv.

not that any of this is doable in the near future, since i'm behind cgnat and won't get my colocated bounce server up until spring.

you are viewing a single comment's thread
view the rest of the comments
[–] 0 points 11 months ago* (1 child)

Sure, software can always be vulnerable. What's the difference between me consuming it from someone else or my private server?

Plex was running on his private computer, not a dedicated server, right? Windows? His version was 75 versions behind the current version at the time. How could the malware escape the server's/plex' sandbox? With a keylogger? Why wasn't he using a password software? This isn't the best example for your point

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 11 months ago

    Plex was running on his private computer, not a dedicated server, right?

    They opened it to the internet - that's the big difference (and the topic at hand). Security is a multi-layered thing, but if your weakest point is a gaping hole, the rest doesn't mean much. To my point - assuming Jellyfin ain't gonna have vulnerabilities even when you're fully up-to-date, is foolhardy.

  • permalink
  • fedilink
  • source
  • parent