I have a friend group that loves dumb American shows playing as background noise, think My Big Fat Gypsies Wedding and Swamp People. It’s hard to easily find all the seasons for them, so my jellyfin instance is a perfect place for them to live 😄
I ran a full scan, but did I miss something about “optimising” the database?
Windows computers maybe? WC for short.
But wasn’t the latest AUR attack from a dependancy in the pkgbuild? Going out of your way to review all the dependencies as well is not really possible by just skimming through the script.
And AOSP does not make a complete system. There are still plenty of binary blobs in both for drivers to get a working phone.
I do agree it’s an odd choice not to fix it, and I do wish they would. But for now it’s a risk I’m fine with taking. If my server gets DOSd in the future from multiple unauthenticated streams I sure will be a grumpy git and complain to them, but in the mean time uuh… sharing is caring? 😅
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. https://github.com/jellyfin/jellyfin/issues/1501
Then there’s the release of 10.11.7 that fixed a number of security issues. https://github.com/jellyfin/jellyfin/releases/tag/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: https://jellyfin.org/docs/general/post-install/networking/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.
Do you have any proof that it’s not secure?
Unfortunately for a Plex style easy to share library you need it to be centralized, handing over a lot of power to whoever is controlling it.
Why not? Unless you’re talking about unauthenticated steaming of media if you reverse engineer a servers folder structure.
*My Band starts playing in the background*
I would assume he means sub 44.1k Hz and 16-bit.