Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Most of these require some form of random id to exploit, which leaves you either brute forcing ids or brute forcing a user account
Again, its not random. It's not a UUID. Its an md5 hash of the filepath. Which is easily guessable since most people have a very similar if not identical folder structure, especially since a lot have it managed by the *arr suite. take that plus the publicly available release names for movies and you're done
Put your files in a randomly named root folder and it's fixed. Even still, isn't the worst they could do pirating your service?
No, the worst is that a company like Sony or their lawyers can find my server and create a list of movies I offer and then sue me over it. I live in a country where lawyers make a living doing nothing but that.
Besides that, security by obscurity is the worst possible form and barely qualifies as security at all. It's also another place where the Jellyfin devs leave their users to their own devices when it comes to securing the server against malicious actors.
And none of this is clearly communicated by the project. The unauthenticated endpoints are not disclosed, the issues with the filepath is not disclosed. Jellyfin fans treat it as a drop in replacement for Plex, but people using it as such basically throw an unauthenticated server onto the open web
In fact security by obscurity is not security at all. In this case it should be authenticated or to the very least to actually use a random string like a uuid. But, changing the root path does prevent it from exploiting. Not perfect but a temporary solution.
Another place? What else? You mean setting up you own server? That is in fact your responsibility.
I live in a country where making copies of movies and having them for private consumption isn't illegal.
I wouldn't blame the Jellyfin devs for this situation, they inherited a lot of bad code from Emby and are still cleaning it up.
The Jellyfin devs have quite clearly outlined some of the issues in the setup guides, and others are detailed in issues on Github. They do work on it, but most bad code was inherited and they have limited time on their hands to fix it, preferably in a way that doesn't instantly mess up everyone's setups.
They could put a banner in the network settings warning users about these security issues while they get them fixed, that doesn't require fixing any inherited code. In the GitHub issue linked, there's at least one upset user because they had no idea this was even a problem.
I mean, that's fine, but it's still an issue and a risk that would cause me to want to use VPN for remote viewing. It doesn't seem like security is Jellyfin's priority at the moment, not that it's Plex's either, but it's not to a place where it's worth it to switch from a security standpoint, personally.
Plex has a whole team dedicated to security. It's obviously not perfect and it is a larger attack surface than Jellyfin, but I'll take that any day over devs who treat security as an afterthought
You mean the security team that got pwned here?
Still better to have a team to react to this incident than just have them shrug and ignore it for 5 years
What about the pwned users of Jellyfin that have unknowingly had security holes for 5 years because Jellyfin doesn't care enough to even put a banner in their settings to say it's not secure?
What security holes? I think the bigger problem here is relying on a media platform to also maintain security protocols. Use authelia or plug some other well maintained and hardened security mechanism on top of jellyfin. Then put it in front of everything else like the arrs, etc. Its weird to me to just setup jellyfin, make it Internet facing, and believing everything is just gonna be safe and secure with no issue. Frankly id prefer if all these services came without security. Its a royal pain to bypass it for localhost or proxying with something like authelia.
Huh? Did you even read the whole thread? They're linked above.
If you hand wave those away then you can’t possibly have any issue with Plex.
I don't have an issue with Plex. I don't use it