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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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.
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
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