Comment on Improve very slow library scans on Jellyfin 10.11 / 12 on spinning media
HereIAm@lemmy.world 2 weeks agoWhy not? Unless you’re talking about unauthenticated steaming of media if you reverse engineer a servers folder structure.
Comment on Improve very slow library scans on Jellyfin 10.11 / 12 on spinning media
HereIAm@lemmy.world 2 weeks agoWhy not? Unless you’re talking about unauthenticated steaming of media if you reverse engineer a servers folder structure.
GoatSynagogue@lemmy.world 2 weeks ago
It’s not secure. It’s a horrible thing to do
HereIAm@lemmy.world 2 weeks ago
Do you have any proof that it’s not secure?
GoatSynagogue@lemmy.world 2 weeks ago
The developers of jellyfin themselves say it’s not.
HereIAm@lemmy.world 2 weeks ago
I think you’ve fundamentally misunderstood some of their communication.
There’s the issue I described earlier where it is possible to stream files unauthenticated if you know the folder structure on the video. The devs have responded that they won’t fix this. Outside of streaming content, there’s no other access through this mean. github.com/jellyfin/jellyfin/issues/1501
Then there’s the release of 10.11.7 that fixed a number of security issues. github.com/jellyfin/jellyfin/releases/…/v10.11.7 with no major security issues since then. And all the issues were privilagr escalation for a normal user account on jellyfin. So the attacker would already needed to have an account on your server, and only the data that jellyfin could see was at risk, nothing escaped contagion so to say.
They also officially support a reverse proxy set up: jellyfin.org/docs/general/…/reverse-proxy/.
I have no idea where you’ve got the idea where they themselves claim it’s unsecure to open it to the internet. Of course there’s always a risk associated with exposing something, but jellyfin doesn’t pose any larger risk than anything else you might publish.