Comment

Comment on Plex vulnerabilities being exploited in the wild to drop a cryptominer

Not if your Jellyfin is set up correctly.

Read-only, rootless container with only the cache/transcode/config folders mounted RW+noexec - ideally both with a volume size limit.

Reverse proxy only the absolutely minimal ports needed, with some security measures (e.g. crowdsec transparent proxy, hooked up to both your firewall and reverse proxy to block malicious actors.

source

Sort:hotnew top

Blue_Morpho@lemmy.world ⁨1⁩ ⁨day⁩ ago
The 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.

source
- fonix232@fedia.io ⁨1⁩ ⁨day⁩ ago
  It's literally just:
  
  create docker container
  
  forward FOUR ports: 8096, 8920, 7359(udp) for discovery, and 1900(UDP) for DLNA to local network
  
  forward a SINGLE port via reverse proxy: 8096 if your proxy handles HTTPS, 8920 if you want Jellyfin to handle HTTPS
  
  I highly doubt that if somehow you were setting up BGPs at Cisco, this incredibly straightforward port setup somehow got the best of you.
  
  source
  - 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”
    
    source
    fonix232@fedia.io ⁨1⁩ ⁨day⁩ ago
    
    First it's a VM because I'm not going mess around with stuff on bare metal.
    
    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".
    
    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.
    
    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.)
    
    Then there's setting up the certificate with the dns provider.
    
    Uh what? ACME makes it a literal one line configuration. Two if you include the DNS host scoped token.
    
    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".
    
    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...
    
    source
    -> View More Comments
- fonix232@fedia.io ⁨1⁩ ⁨day⁩ ago
  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.
  
  source