Collision, not pre-image attack (the two are different)

This is FUD. There is no publicly known pre-image attack against SHA1, the hash used in mainline DHT.

Do not expose Jellyfin to the general Internet. They have security issues, I would not trust that (no cloudflare does not save you by default).

There are basically two ways: VPN, or authenticated reverse proxy. VPN is probably the easiest to setup and the most flexible, but it’s a bit of a pita to use.

Authenticated reverse proxy will break apps, but the web app will work (and you can setup your reverse proxy to allow specific user agents from the VPN to bypass it, allowing apps on the VPN to work). I currently do this so I can look at metadata on my phone without a VPN setup.

You don’t even need the vps unless you’re behind cgnat Though you should never expose Jellyfin to the Internet, they have had and continue to have major security problems

I use a Firefox container tied to a socks proxy on my router to bypass VPN for tricky sites. Yeah I know not the answer you’re looking for but some things have to be done (banking, health insurance) and if they already know my home address there’s little reason to hide the IP address

Fair, have never looked at the price, I just have a Linux mini PC running Jellyfin lol

Passwords will be brute forced if it can be done offline.

Set a good high entropy password, you can even tie it to your login password with ssh-agent usually

Private SSH keys should never leave a machine.

If this actually matters, put your SSH key on a yubikey or something

If a key gets compromised without you knowing, in worst case you will revoke the access it has once the machine’s lifespan is over.

People generally don’t sit on keys, this is worthless. Also knowing people I’ve worked with… no, they won’t think to revoke it unless forced to

and you will never revoke the access it has.

Just replace the key in authorized_keys and resync

And you may not want to give all systems the same access everywhere

One of the few reasons to do this, though this tends to not match “one key per machine” and more like “one key per process that needs it”

Like yeah, it’s decent standard advice… for corporate environments with many users. For a handful of single-user systems, it essentially doesn’t matter (do you have a different boot and login key for each computer lol, the SSH keys are not the weak point)

If the keys are password protected… eh why not sync them.

Also ssh certificates are a thing, they make doing that kind of stuff way easier instead of updating known hosts and authorized keys all the time

Sounds like a pain to get non technical family members to use. If you’re willing to break the non web app you could always put it behind an authenticating proxy (which is what I do for myself outside of VPN, setting up a VPN on a phone is obnoxious and I only look at metadata anyway on my phone)

There’s an addon for that (I haven’t used it)

Why not just attach a non shitty device over HDMI and use that?

Lots of people do that, the Nvidia shield is one I hear a lot about

Hint: you don’t have to use ldap to use authelia (I haven’t bothered). It’s a bit awkward to use though, I’d only recommend it for single-user setups (I wish they would just add support for SQLite, they already use it for 2fa and stuff)

Potentially stability improvements as well (for the same reasons as the security improvements), especially for lesser used drivers and stuff.

Do authentication in the reverse proxy if you can (e.g., basic auth or forward auth like Authelia, the second also has the benefit of SSO).