I don’t really agree with you here. If you take the time to set things up properly. And prepaid for IF something would happen. Your fine. Been running a exposed jellyfin server for years now. Never hat a security issue. And even if I would not much harm could be done anyway due to how it is setup.
Comment on Moving from Cloudflare tunnels for media streaming, first plan didn't work out due to double NAT
SirMaple__@lemmy.ca 3 weeks ago
Do not. I repeat do not expose Jellyfin to the internet. It has too many security issues to be direct accessible from the internet.
I use Jellyfin and only access it over WireGuard. I have a mesh setup between the routers at a few family members houses.
If you have absolutely no other way then to expose it to the internet you need to make sure that you whitelist only the approved IPs in your VPS firewall and block everything else.
kylian0087@lemmy.dbzer0.com 3 weeks ago
SirMaple__@lemmy.ca 3 weeks ago
[deleted]Auli@lemmy.ca 3 weeks ago
Have you even looked at what you are posting? Most of those are fixed. And most are who cares.
chriscrutch@lemm.ee 3 weeks ago
Thanks for mentioning that. I’ll have to look into it. If I could install Tailscale on a RokuTV I’d absolutely run it that way.
ladfrombrad@lemdro.id 3 weeks ago
I haven’t seen no one mention it yet but you could simply buy a Rasp Pi and use it as a subnet router for your Tailnet.
It’s how I set up a family members Jellyfin/NAS/etc which I can access all their devices by local IP address, and you could do for your Roku too?
L_Acacia@lemmy.ml 3 weeks ago
you can add authentic/authelia with keys for login and it should be fine
lostbit@feddit.nl 3 weeks ago
bullcrap,show me those security issues
Max_P@lemmy.max-p.me 3 weeks ago
I keep hearing claims that it’s not secure enough to be exposed on the Internet, but I can’t seem to find anything about unauthenticated vulnerabilities. It’s got a fair amount of CVEs but they all seem to affect when you’re an already authenticated user, mainly to XSS an admin as a regular user or the likes.
It’s written in C#, and publicly all you can do is pretty much attempt to log in, this feels like it should be pretty sane compared to some other PHP crap I run.
Do you have any examples of previous exploits or anything else to be concerned about?
SirMaple__@lemmy.ca 3 weeks ago
Strit@lemmy.linuxuserspace.show 3 weeks ago
Most of the relevant issues they link to has been closed and/or dealt with.
ChapulinColorado@lemmy.world 3 weeks ago
You don’t have to take my word on this, but when you have so many vulnerabilities, the foundation and knowledge about security practices by the developers is missing some key ingredients.
I use Jellyfin. I like jellyfin. I would like people to use jellyfin, but do it responsibly.
Citing backwards compatibility is not an acceptable answer either. If individual endpoints and/or protocols (web sockets) are being addressed as separate issues, then there is no overall filter for the most basic thing as checking if the user is authenticated, you know a potential attacker will look for more.
Will they target jellyfin instead of your average government website with a low budget and similar issues? Unlikely, but possible if the level of effort is low and can potentially create a large botnet, maybe?
You handle these with overall filters (or whatever they are called on c#) and white lists if something truly needs not to have it instead of reacting when someone reports it.
The simple fact that some of the code was sending api keys as GET parameters (which get logged cross every access log in the middleware on its way to the target server) and it didn’t raise any flags seems sufficient enough to suggest DO NOT expose jellyfin directly to the internet.