Comment

Comment on How do I host Jellyfin in the most secure manner possible?

This would mean that you only want to access Jellyfin when you, and the device you are watching your show/movie on, are at home, where the Pi/server also is.

Is this correct?

Yes.

If so, then questions about VPN, Certificates, DNS,… do not matter.

They do, because if ProtonVPN blocks LAN connections then the only other option is exposing the server to the WAN

open the Jellyfin app on your TV/Phone/PC, connect to 192.168.10.20:8096

This does not encrypt during transit, and my network is not a trusted party.

I honestly fail to see where a VPN would even come into the equation here

I, like many others, use my devices for more than just accessing my LAN while I am on my home network.

source

Sort:hotnew top

smiletolerantly@awful.systems ⁨1⁩ ⁨week⁩ ago

This does not encrypt during transit, and my network is not a trusted party.

Then honestly, you have other problems than setting up Jellyfin.

For real though, if you think someone is (or might be) listening in on your local network, i.e. have physical access or compromised one of your machines, then the Jellyfin traffic is the least of your problems. Pick your battles. What’s the worst that could happen here - someone gets to know your favorite show?

They do, because if ProtonVPN blocks LAN connections then the only other option is exposing the server to the WAN

Ah, I see. On your PC you should just be able to set a static route over the physical interface for 192.168.0.0/24 (or whatever your local network is) which takes precedence over the VPN. For android… Oof, no idea. Probably need root.

source
- Charger8232@lemmy.ml ⁨1⁩ ⁨week⁩ ago
  
  For real though, if you think someone is (or might be) listening in on your local network, i.e. have physical access or compromised one of your machines, then the Jellyfin traffic is the least of your problems. Pick your battles. What’s the worst that could happen here - someone gets to know your favorite show?
  
  A bad router + bad ISP combo means I get ratted out for copyrighted material (that I don’t have… I only host creative commons videos on my Jellyfin server, of course…)
  
  source
  - smiletolerantly@awful.systems ⁨1⁩ ⁨week⁩ ago
    This isn’t really true. Even IF your router would fail catastrophically in the right way to expose your Server to the internet, or of it actually “ratted your traffic out” to the ISP and the ISP cared (which it does not), it’s not illegal to hist Jellyfin, or put media on it which you own (which is not discernible from just… Media being streamed).
    
    Also your ISP has no part in your local network traffic.
    
    source
  - Trainguyrom@reddthat.com ⁨1⁩ ⁨week⁩ ago
    Sounds far more likely that either someone misunderstood that residential IPs change frequently/may be shared by multiple subscribers or the ISP made an error when responding to a subpeana and provided the incorrect IP. Unfortunately both are all too common with privacy enforcement
    
    If you really think the ISP router is snooping and can’t by bypassed you could simply double-NAT your network with a trusted router and call it a day. Much less VPNing and much less unusual decisions of trust and threat model involved then
    
    source
skizzles@lemmy.world ⁨1⁩ ⁨week⁩ ago
Just out of curiosity, why is your network not a trusted party?

You could start with an additional firewall and maybe setting up traffic restrictions on it to mitigate what devices can communicate with each other, in addition to setting up a local VPN.

Yes its possible to spoof mac addresses and such but it really sounds like your concerns could be mitigated by having a more secure network setup.

If your network isn’t a trusted party then you need to start there. Why isn’t it a trusted party and what do you need to do to secure the traffic to/through it.

source
- Charger8232@lemmy.ml ⁨1⁩ ⁨week⁩ ago
  
  Just out of curiosity, why is your network not a trusted party?
  
  Part of my threat model is essentially “anything that can connect to the internet poses a security risk”. Since networks are the literal gateway to the internet, it is reasonable not to trust them. Routers don’t run as secure operating systems as Qubes OS, secureblue, or GrapheneOS. If a malicious party found a way to connect to the network, all unencrypted activities can be intercepted. If the router itself has malicious code, any unencrypted traffic can be sent to a third party. Those are just the basics, but trying to put band-aid solutions on a fundamentally broken system is a losing battle.
  
  GrapheneOS distrusts networks as much as possible, so I do too. Even if I own the network, I am not a network engineer, so the chances of fault are high. In the simplest case, the network is a gateway to all activity that happens on the LAN, and it only takes one zero day to make that happen. The best mitigation is proper encryption and no self-signed certificates (where possible).
  
  source