668
Jellyfin critical security update - This is not a joke (github.com)
submitted 7 months ago by to c/selfhosted@lemmy.world
183 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 26 points 7 months ago (5 children)

There is a good reason I only have Jellyfin and other services accessible via valid Client Certificate.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 8 points 7 months ago (2 children)

    Does it work with android and TV apps?

    I tried long ago and failed.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 14 points 7 months ago* (1 child)

    No, we only use Jellyfin via browser. Unfortunately even with imported Client Cert, Android apps won't work.

    Edit: Client Certs need to be implemented per App. There is a feature request from 2022 https://features.jellyfin.org/posts/1461/capability-to-specify-client-certificate-for-android-client

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago (1 child)

    Also interested how this works for mobile apps. I self host a number of services through caddy as my reverse proxy but each application is just dependent on it's own authentication. If I exposed all my services to the internet, that's a huge attack vector. If anyone else has some ideas I'd be happy to listen.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago

    If you are the only user and don't need to use those apps in devices you don't own a vpn is the way to go.

    If not. Depending the number of users you could do some heavy ip geoblocking to at least reduce the exposed surface.

    There are a few services I have just like 3 IPs allowed to get a response from caddy, any other ip gets 403 error.

  • permalink
  • fedilink
  • source
  • parent