Jellyfin has plenty of issues with public instances too. It's just the reality of exposing to the public internet, unless it's something that has a lot of dedicated work going into security it's going to have problems.
post
My Plex is updated, and hiding behind a random-long-text-string wildcarded subdomain that (so far) has not been discovered.
My Crowdsec intercepted 5X the normal number of hacking attempts & port scans on October 17th... no doubt from dirtbags trying to exploit this.
Also I use Jellyfin btw.
Oh god, its the new Arch isn't it...
I'm waiting to see the elusive Arch, Jellyfin Vegan stack in the wild. We know they exist and they are fucking telling everyone
No nix is the new arch.
Lol
Sure explains why Plex was so cagey and uninformative when they emailed everyone to update their servers a couple months back. Not so much as a CVE report or change set.
A vulnerability? No…. 4 of them. And they stack.
I just assumed it was because it lined up with them destroying the GUI, the new layout is the hot garbage that finally got my wife to opt for jellyfin.
That kind of is the proper way to handle this. You don’t want to hint bad actors where to look and give people some time to update.
top 50 comments