Selfhosted

46290 readers

473 users here now

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!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Sharing Jellyfin (poptalk.scrubbles.tech)

submitted 13 hours ago by scrubbles@poptalk.scrubbles.tech to c/selfhosted@lemmy.world

64 comments fedilink hide all child comments

Hi folks. So, I know due to a myriad of reasons I should not allow Jellyfin access to the open internet. However, in trying to switch family over from Plex, I'll need something that "just works".

How are people solving this problem? I've thought about a few solutions, like whitelisting ips (which can change of course), or setting up VPN or tail scale (but then that is more work than they will be willing to do on their side). I can even add some level of auth into my reverse proxy, but that would break Jellyfin clients.

Wondering what others have thought about for this problem

you are viewing a single comment's thread
view the rest of the comments

[–] skankhunt42@lemmy.ca 1 points 13 hours ago (2 children)

Hang on, why not open the port to jellyfin to the internet?

I have a lifetime Plex pass so its not urgent but I have a containers running emby and jellyfin to check them out. When I decide which one I planned to open it up and give people logins.

[–] possiblylinux127@lemmy.zip 1 points 1 hour ago

That wouldn't even be using TLS

Bad idea

[–] Selfhoster1728@infosec.pub 10 points 13 hours ago* (last edited 13 hours ago) (1 children)

See this issue on their github repo: here

Basically from what I understand there's loads of unauthenticated api calls, so someone can very easily exploit that.

If they just supported mTLS in their clients it wouldn't be an issue but oh well :(

[–] exu@feditown.com 3 points 7 hours ago (1 children)

The main unauthenticated action is video streaming, but an attacker would need to guess the correct id by chance.

https://github.com/jellyfin/jellyfin/issues/5415#issuecomment-2825240290

[–] MaggiWuerze@feddit.org 3 points 7 hours ago

It's not chance if the I'd is based on the path to your media. There's but that much variation in the path to a certain movie and its trivial to build a rainbow table to try them out. This way unauthenticated users can not only stream from your server but effectively map your library