Comment on Improve very slow library scans on Jellyfin 10.11 / 12 on spinning media
blue_morpho@lemmy.world@lemmy.world 3 weeks agoHe said an encrypted tunnel does nothing. I don’t even run Jellyfin but that statement is false.
Comment on Improve very slow library scans on Jellyfin 10.11 / 12 on spinning media
blue_morpho@lemmy.world@lemmy.world 3 weeks agoHe said an encrypted tunnel does nothing. I don’t even run Jellyfin but that statement is false.
An encrypted tunnel and a reverse proxy are Ber different things. He (I) never talked about a tunnel and neither did the comment I (he) responded to
blue_morpho@lemmy.world@lemmy.world 3 weeks ago
The reason to run the reverse proxy with Jellyfin is for the encryption. It’s written in the documentation that way. It’s why I still run Plex. I never finished getting through their steps to get the reverse proxy setup for the encryption.
It’s like I said you use a car to go to work and you reply AKSUALLY a car runs on TIRES. The OP didn’t say CAR.
Having an https connection doesn’t do shit if the Backend is insecure. The issue with exposing Jellyfin are not man in the middle attacks, but badly managed access controls and unsecured endpoints.
Thede issues and the unwillingness of the devs to fix them because they are hellbent on keeping a maximum of client compatibility is what makes it hard to trust the overall security of the project.
That’s why basically everyone, including the devs, says to not do that and instead rely on a vpn to mitigate security risks.