Yup! That’s the worst thing that can happen. Now would you be so be kind as to send us the link to your private unsecured Jellyfin server?
Comment on Why I moved my Plex library to Jellyfin after 14 years
Evotech@lemmy.world 3 weeks agoWhat’s the worst that can happen. Someone watches your movies
InputZero@lemmy.world 3 weeks ago
Evotech@lemmy.world 3 weeks ago
I’m tempted to. But I’m not. Just because I dont want to fox my domain here.
Is running in a rootless podman container. I’m confident
GreenKnight23@lemmy.world 3 weeks ago
Someone breakes in, then moves laterally to your home assistant running frigate to watch you sleep at night. Then uses your residential uplink as a proxy to resell on an open market.
After that, the possibilities are practically endless.
Evotech@lemmy.world 3 weeks ago
It’s a rootless container. Chances are they are not going to do any of that.
InputZero@lemmy.world 3 weeks ago
Yeah docker isn’t the isolation sandbox some people make it out to be. It’s not meant for that. You very well may have a setup that’s meant for that but it’s more than I’m willing to expose.
klankin@piefed.ca 3 weeks ago
No reason to connect jellyfin to any sort of local network, router will still hairpin for local connection.
With that setup its honestly more secure than 99% of IOT devices, and like 50% of routers.
kalpol@lemmy.ca 2 weeks ago
Good grief. If you’re doing all that, just set up Wireguard
klankin@piefed.ca 2 weeks ago
I mean containers make the networking pretty easy, everything beyond that is optional based on your threat model.
Same as hosting anything networked, you can do it easy or do it safe.
(but also wireguard is kinda an O(n) problem while exposing to wan is an O(1) problem - at least IT man hours wise)