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.
How often do you read that a jellyfin server was compromised?
I mean, anything with a web server can have vulnerabilities. Just look at the LastPass breach where hackers got in through an employee’s exposed Plex library.
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
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.
Not every compromise is reported, or even detected.
If it’s not detected, reported and noone gets hurt, what’s the problem?
How do you know no one is being “hurt”?
How are you hurt if your jellyfin server is compromised and you don’t know about it?
That’s not a serious question, is it?
Hackers don’t report every time they hack someone, nor how they did it.
Jellyfin has a laundry list of security problems because it’s not designed to be directly exposed to the open internet