• 0 Posts
  • 7 Comments
Joined 11 months ago
cake
Cake day: June 27th, 2025

help-circle


  • Depends on what you mean by “secure.” My personal setup is Jellyfin LXC on proxmox --> Wireguard to VPS -> Nginx reverse proxy on VPS.

    This setup relies somewhat on Jellyfin’s auth, but I’m comfortable with that risk. The LXC is blocked from sending local traffic on my network by firewall rules. Yes, someone could exploit a vulnerability in Jellyfin (though looking through the CVEs I’m not overly worried about that), then escape the LXC and fuck with my server. But that’s a lot of work for no profit.

    For more protection (in sense of reducing traffic that even interacts with your server), I’d recommend getting a wildcard cert for the domain so that the actual subdomain jellyfin is on is undisclosed to anyone not using your service.

    Security isn’t about making everything impregnable, it’s about making attacks more trouble than they’re worth. Otherwise, we’d all live in fortified bunkers surrounded by landmines. 🙃




  • It’s not just about moral reasons (although I would write them off for moral reasons alone, to be clear). Brave as a browser has a history of making privacy worse- see, for example, disabling advance anti-fingerprinting in 2024 and their piss-poor tor implementation in 2021. Your initial comment had said you hadn’t seen anything since 2018 and maybe you like the browser enough to not care about their history of careless implementations of privacy features or their limiting of user choice on fingerprinting protections, but I don’t see how these objections can be dismissed as not relating to privacy.