Comment on Plex vulnerabilities being exploited in the wild to drop a cryptominer
Blue_Morpho@lemmy.world 1 day agoThe start of this thread is “number one reason people don’t move to Jellyfin is ease of remote access.”
30 years ago I was compiling slackware and configuring dns servers, and setting up BGP on Ciscos. But a few hours of attempting to setup Jellyfin was a failure. It was far more complex than setting up dns/bind.
Beside, that wasn't even the topic. We were discussing - or rather, I was proving to the above commenter - that setting up Jellyfin in a way that does not allow an intruder to crypto mine or host CSAM or use your device as a proxy, is incredibly easy.
Port setup and it's perceived impossibility by you has naught to do with that topic.
fonix232@fedia.io 1 day ago
It's literally just:
I highly doubt that if somehow you were setting up BGPs at Cisco, this incredibly straightforward port setup somehow got the best of you.
Blue_Morpho@lemmy.world 1 day ago
Not at Cisco. With a Cisco. I ran a mid sized ISP in the 90’s until I was bought out by a cable company and retired. Although several of my employees went on to work at Cisco. I also had a few friends who were executives at Cisco because we all started at a company working for Vint Cerf and Bob Khan (they were the angel investors) back before most knew of the Internet.
First it’s a VM because I’m not going mess around with stuff on bare metal. Create docker is a can of worms because you have to pick a reverse proxy software like nginx, traefik, caddy. Which means you need to understand all three to know which to pick. Then there’s setting up the certificate with the dns provider. So I got nginx working with a certificate but gave up after the VM running Jellyfin couldn’t see it. Googling showed someone on Reddit with the same problem but no answer other than others saying “works for me”
fonix232@fedia.io 1 day ago
Containerisation method doesn't matter, the point is to have an untrusted container (VM, thin container, LXC, whatever) that a process cannot exit, has no root user rights, and can be limited externally for what resources it sees.
The entire point is to be able to say "here's your config folder where you can write shit, but not execute; here's the data folder where you can neither write or execute shit; and here's the read-only executable layer of the image/VM/container".
Regardless how you're hosting it, a reverse proxy is necessary. Even with a VM.
Here's a fun fact: Caddy and Traefik both come with ways to easily configure all the necessary things via Docker container labels. I need about 3-4 labels per container to set up the subdomain I need, the port I want to forward to it, and the security level (auth, crowdsec, etc.)
Uh what? ACME makes it a literal one line configuration. Two if you include the DNS host scoped token.
So the problem wasn't Jellyfin but you not being able to follow a dead simple guide. And to think you were running a whole ass ISP...
Blue_Morpho@lemmy.world 1 day ago
The fact that others had the same problem without solution means it isn’t follow a dead simple guide. There are multiple guides. Just setting up docker means you have to already know to not use it and run podman. Because if you follow the online guides on docker’s own website, you end up with a docker gui and their AI assistant installed.
You are arguing that setting up an Internet server is as simple as it was 30 years ago. You are arguing for the sake of arguing.