Selfhosted

60542 readers

581 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:

Detailed Rules Post

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.
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.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What's the security situation when opening a jellyfin server up for casting? (feddit.nu)

submitted 7 months ago by lime@feddit.nu to c/selfhosted@lemmy.world

76 comments fedilink hide all child comments

when reading through the jellyfin with chromecast guide i realized that it would probably be less effort to just let the casting api be public, with the added bonus that i could then cast my library to any device that supports it. but that seems like it would paint a giant target on the server.

what's the recommended way of doing stuff like this? ideally i want to be able to go to someone's house and just play some of my media on their tv.

not that any of this is doable in the near future, since i'm behind cgnat and won't get my colocated bounce server up until spring.

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

[–] droolio@feddit.uk 7 points 7 months ago (1 children)

I mean, anything with a web server can have vulnerabilities. Just look at the LastPass breach where hackers got in through an employee's exposed Plex library.

[–] illusionist@lemmy.zip 0 points 7 months ago* (last edited 7 months ago) (1 children)

Sure, software can always be vulnerable. What's the difference between me consuming it from someone else or my private server?

Plex was running on his private computer, not a dedicated server, right? Windows? His version was 75 versions behind the current version at the time. How could the malware escape the server's/plex' sandbox? With a keylogger? Why wasn't he using a password software? This isn't the best example for your point

[–] droolio@feddit.uk 2 points 7 months ago

Plex was running on his private computer, not a dedicated server, right?

They opened it to the internet - that's the big difference (and the topic at hand). Security is a multi-layered thing, but if your weakest point is a gaping hole, the rest doesn't mean much. To my point - assuming Jellyfin ain't gonna have vulnerabilities even when you're fully up-to-date, is foolhardy.